Matthias Klose, le lun. 18 mai 2020 15:49:40 +0200, a ecrit: > On 5/18/20 3:28 PM, Samuel Thibault wrote: > > Matthias Klose, le lun. 18 mai 2020 15:25:41 +0200, a ecrit: > >> On 5/18/20 2:59 PM, Samuel Thibault wrote: > >>> It seems hurd-i386 was left with building with --with-arch=i586, while > >>> there is no reason any more to do so. I checked building glibc, hurd, > >>> gnumach, without any issue. > >> > >> is it really correct to omit this configure option, instead of setting it > >> to > >> i686 explicitly? > > > > i686 is already inherited from dpkg-architecture's output: > > > > DEB_TARGET_GNU_CPU=i686 > > DEB_TARGET_GNU_SYSTEM=gnu > > DEB_TARGET_GNU_TYPE=i686-gnu > > > > (just like on linux-any and kfreebsd-any). > > the TARGET macros are overridden because dpkg should not define the baseline. > The target macros are also bogus in case a package builds for multiple > targets. > > I'll set that directly.
I'm a bit lost as to why you seem to think something needs to be set explicitly. AIUI, for linux-i386 and kfreebsd-i386 nothing explicitly says to use i686. I'm just saying that there is nothing to say for hurd-any either (and certainly not request i586 which is an old remnant from previous toolchains). And I did try to use that compiler, it does produce i686 code, so it does have the desired effect of just behaving like linux-any and kfreebsd-any, instead of having a special case for hurd-any. Samuel
