re: retiring arm oabi support for new things
i think we're missing -m evbarm -a earmv4 builds, which should create an evbarm set targetting our speical eabi on armv4, and that "normal" earm builds should elide them. shouldn't be too hard, we already collect them eg, into $EVBARM_BOARDS.armv4. thanks for pointing that out! .mrg.
re: retiring arm oabi support for new things
> >netbsd 9 will ship without any targets with oabi as the > >default, and most of the existing ports were already > >switched to eabi (epoc32 and acorn32 only.) > > > >as part of this, i'm going to stop providing the ability > >to build any arm with oabi -- turn off the MKCOMPAT for > >all arm ports, so the oabi libraries are not provided > >anymore, turn off the oabi ld.elf.so, etc. > > Are you going to change the compiler target name as part of this ? > > I'm currently struggling with an autoconf script that is getting > confused by the -eabihf part of the armv7--netbsdelf-eabihf name. i wasn't going to change any names. target names have meaning and shouldn't change, it's way too late to change this now. patch the script to be smarter is the only real option or we would break all the existing things that already know what each target is is the only sane response.. .mrg.
Re: retiring arm oabi support for new things
matthew green wrote: >netbsd 9 will ship without any targets with oabi as the >default, and most of the existing ports were already >switched to eabi (epoc32 and acorn32 only.) > >as part of this, i'm going to stop providing the ability >to build any arm with oabi -- turn off the MKCOMPAT for >all arm ports, so the oabi libraries are not provided >anymore, turn off the oabi ld.elf.so, etc. Are you going to change the compiler target name as part of this ? I'm currently struggling with an autoconf script that is getting confused by the -eabihf part of the armv7--netbsdelf-eabihf name. I have been building arm targets with MKCOMPAT=no for a long time now so no problem with the proposed change.
retiring arm oabi support for new things
hi folks. netbsd 9 will ship without any targets with oabi as the default, and most of the existing ports were already switched to eabi (epoc32 and acorn32 only.) as part of this, i'm going to stop providing the ability to build any arm with oabi -- turn off the MKCOMPAT for all arm ports, so the oabi libraries are not provided anymore, turn off the oabi ld.elf.so, etc. i will not be removing the ability to execute these binaries, but their supplimental files (ld.so, shlibs) will need to be supplied from a prior release if the old binaries are still required. there should not be any issue here, as the kernel support is fairly simple and doesn't need to change. i'm pretty sure this won't affect anyone. if you have upgraded to an eabi release, with oabi shlibs provided, you were already happy. if you're running very old netbsd, then upgrading to netbsd-9 and then beyond will be the solution to keep your shlibs at highest level. this should reduce the build time of the whole cluster. there are about 15 arm ports in total, and turning off all their shlib builds will probably save a noticeable fraction of the total. any comments? .mrg.
