Re: Default value for CFLAGS/LDFLAGS set by dpkg
Raphael Hertzog wrote:
> Hello,
>
> a few days ago we had a discussion on IRC about numerous problems created
> by a change in dpkg-dev:
> - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465282
> - http://git.debian.org/?p=dpkg/dpkg.git;a=commit;h=a143d3b44001f328453e0b71d272e06eb60903fa
>
> doko pointed out that several packages had to be updated to cope with the
> change and most notably the libc which had a run-time failure due to the
> default value set to LDFLAGS.
>
> A rebuild by Lucas also showed around 80-100 packages which FTBFS with this
> version of dpkg-dev.
>
> Last I heard Frank (djpig) and Andreas (aba) were discussung together the
> issue but I haven't seen any decision yet. Given that I want to prepare
> dpkg for the next upload, I'd like that we take a decision on this issue.
>
> I'd like to suggest an intermediary solution: we don't revert the feature
> but we remove the default value for LDFLAGS. I think that most run-time
> and build-time failures have been caused by the change on this variable.
>
> Does that seem acceptable? For lenny+1, we can reintroduce the original
> default value.
Sounds overall reasonable to me, however, I'm in doubt about using
-Bsymbolic-functions as a global default. I presume (without having
read up on it) that it breaks symbol preemption as defined in the ELF
gABI standard.
Thiemo
Reply to: