From: Ed M. <em...@fr...> - 2015-07-27 18:49:19
|
I have a review open for FreeBSD[1] to install elfcopy as objcopy, but before going ahead I'd like to understand the original motivation for giving the tool a distinct name in ELF Tool Chain. We support formats other than just ELF, although the list is smaller than GNU objcopy's. This is also true for other ELF Tool Chain tools though, and anyone installing both ELF Tool Chain and other compatible tools is going to need to set PATH appropriately or explicitly choose their tools somehow. Given this, is there a reason I shouldn't install it as objcopy? [1] https://reviews.freebsd.org/D2887 |
From: Kai W. <kai...@gm...> - 2015-07-27 19:02:54
|
Hi Ed, elfcopy was among the first tools we implemented in the toolchain and we thought we could name it elfcopy since we planned to only support ELF format. Then later when we implemented other tools we figured the "elf" prefix seems to be inappropriate, but we were too lazy to change it back. elfcopy now supports srex, ihex, binary formats etc, and I plan to add PE support also. So it's more or less a misnomer now... anyway I think it's ok we install it as objcopy under FreeBSD. /Kai On Mon, Jul 27, 2015 at 8:48 PM, Ed Maste <em...@fr...> wrote: > I have a review open for FreeBSD[1] to install elfcopy as objcopy, but > before going ahead I'd like to understand the original motivation for > giving the tool a distinct name in ELF Tool Chain. We support formats > other than just ELF, although the list is smaller than GNU objcopy's. > This is also true for other ELF Tool Chain tools though, and anyone > installing both ELF Tool Chain and other compatible tools is going to > need to set PATH appropriately or explicitly choose their tools > somehow. Given this, is there a reason I shouldn't install it as > objcopy? > > [1] https://reviews.freebsd.org/D2887 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Elftoolchain-developers mailing list > Elf...@li... > https://lists.sourceforge.net/lists/listinfo/elftoolchain-developers > |
From: Ed M. <em...@fr...> - 2015-07-27 19:32:43
|
On 27 July 2015 at 15:02, Kai Wang <kai...@gm...> wrote: > Hi Ed, > > elfcopy was among the first tools we implemented in the toolchain and we > thought we could name it elfcopy since we planned to only support ELF > format. > Then later when we implemented other tools we figured the "elf" prefix seems > to be inappropriate, but we were too lazy to change it back. > > elfcopy now supports srex, ihex, binary formats etc, and I plan to add PE > support also. > So it's more or less a misnomer now... anyway I think it's ok we install it > as objcopy > under FreeBSD. Kai, thanks for the information. I'll go ahead with the change, which installs as objcopy by default only on arm64 right now (since the GNU objcopy in FreeBSD base does not have arm64 support), and enable it by default on all platforms once all required functionality is implemented. As far as I know PE support is the only blocking issue -- we need it to produce the x86 UEFI boot bits. |