Re: Bug#594179: dpkg armhf patch acceptance status?
Hello,
2011/2/21 Jonathan Nieder <jrnieder@gmail.com>:
> That leaves two remaining questions:
>
> - can each Debian arch have a distinct toolchain? If not, why not
> (since it would be very convenient to use)?
The short answer seem to be no, GCC upstream does not like the idea to
have different triplets for those architectures, extending libc
triplet value to encode calling conventions. If I understand correctly
that is what dpkg maintainers would like to see.
> - how do we communicate distinct compiler flags for the build and host
> machines to packages, with a minimum of disruption to existing
> packaging? Maybe dpkg-buildflags needs to distinguish between
> --build and --host flags, so that dh_auto_configure et al can pass
> HOST_CFLAGS to configure.
Yet another thought, Debian architecture maps to MAtuples, which then
sets defaults on the toolchain via specs file.
Does it change something if we use (armel) libgcc1 with armhf specs
file, rather than have a libgcc1 defaulting for armhf at (cross-)build
time?
Best regards,
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
Reply to: