Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 30.09.09 19:36, Nix (n...@esperi.org.uk) wrote: > > On 30 Sep 2009, Lennart Poettering said: > > No, --as-needed is a klduge. We explicitly don't support that because > > there is a cyclic dep between libpulse and libpulsecommon. Try to > > google or grep the archives for an explanation for that. > > You might want to add a -Wl,--no-as-needed then, 'cos more and more > distros are turning this on by default (usually by hacking GCC's default > specs). It really is a seriously good idea for the vast majority of > applications. (Last time I measured this it reduced the number of > DT_NEEDEDs across the whole system by in excess of a third.) I think using --as-neded is crack and people don't know what they are doing when they use this. That said I'd be willing to merge a patch that adds -Wl,--no-as-needed to LDFLAGS if it is supported, just to avoid further bug reports about this. Would you be willing to cook up a patch? Thanks, Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 2009-09-30 at 17:50 +0200, Lennart Poettering wrote: > On Wed, 30.09.09 16:08, Ng Oon-Ee (ngoo...@gmail.com) wrote: > > > > > On Wed, 2009-09-30 at 15:54 +0800, Ng Oon-Ee wrote: > > > Sorry, I was just wondering whether its a known issue. When I try to > > > compile with CHOST=x86_64-pc-linux-gnu, I get errors about undefined > > > reference to `lt__PROGRAM__LTX_preloaded_symbols` in various functions. > > > If you wish the exact error messages I can pastebin it. > > > > > Since someone asked me on the IRC, I guess I'll just send the pastebin > > over... > > > > http://pastebin.com/mfa5eff8 > > The interesting line is this: > > libtool: link: not configured to extract global symbols from dlpreopened files > > So this seems to be related to libtool. > > Lennart > Thanks Lennart, I'll chase this down and revert. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On 30 Sep 2009, Lennart Poettering said: > No, --as-needed is a klduge. We explicitly don't support that because > there is a cyclic dep between libpulse and libpulsecommon. Try to > google or grep the archives for an explanation for that. You might want to add a -Wl,--no-as-needed then, 'cos more and more distros are turning this on by default (usually by hacking GCC's default specs). It really is a seriously good idea for the vast majority of applications. (Last time I measured this it reduced the number of DT_NEEDEDs across the whole system by in excess of a third.) > Also, what's the point? I am pretty sure I can come up with lots of > options that make PA fail to build, but why should that matter? For > example I am quite sure that CFLAGS=--oh-lets-break-things makes the > PA build fail. Yeah, but --oh-lets-break-things isn't being turned on by default by the majority of distros. --as-needed pretty much is by now, it's the way shared library linkage was always intended to work and the toolchain developers are thinking of flipping it on by default fairly soon. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 30.09.09 16:08, Ng Oon-Ee (ngoo...@gmail.com) wrote: > > On Wed, 2009-09-30 at 15:54 +0800, Ng Oon-Ee wrote: > > Sorry, I was just wondering whether its a known issue. When I try to > > compile with CHOST=x86_64-pc-linux-gnu, I get errors about undefined > > reference to `lt__PROGRAM__LTX_preloaded_symbols` in various functions. > > If you wish the exact error messages I can pastebin it. > > > Since someone asked me on the IRC, I guess I'll just send the pastebin > over... > > http://pastebin.com/mfa5eff8 The interesting line is this: libtool: link: not configured to extract global symbols from dlpreopened files So this seems to be related to libtool. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 30.09.09 15:54, Ng Oon-Ee (ngoo...@gmail.com) wrote: > On Wed, 2009-09-30 at 09:31 +0200, Lennart Poettering wrote: > > On Wed, 30.09.09 15:22, Ng Oon-Ee (ngoo...@gmail.com) wrote: > > > > > I'm using Archlinux 64-bit (x86_64), and am having trouble compiling > > > pulseaudio from git (or even release tarballs) unless CHOST is > > > x86_64-unknown-linux-gnu. By default my CHOST is x86_64-pc-linux-gnu. Is > > > this an issue with something being hardcoded to the pulse makefiles? > > > Easy to work around, though. > > > > Can you be a bit more elaborate than this? "having trouble" does not > > give me the slightest hint what might be going wrong. > > > > PA itself certainly doesn't check CHOST. > > Sorry, I was just wondering whether its a known issue. When I try to > compile with CHOST=x86_64-pc-linux-gnu, I get errors about undefined > reference to `lt__PROGRAM__LTX_preloaded_symbols` in various functions. > If you wish the exact error messages I can pastebin it. That sounds like an issue with libtool. You probably should bring this to the attention of the lt developers. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 2009-09-30 at 15:54 +0800, Ng Oon-Ee wrote: > Sorry, I was just wondering whether its a known issue. When I try to > compile with CHOST=x86_64-pc-linux-gnu, I get errors about undefined > reference to `lt__PROGRAM__LTX_preloaded_symbols` in various functions. > If you wish the exact error messages I can pastebin it. > Since someone asked me on the IRC, I guess I'll just send the pastebin over... http://pastebin.com/mfa5eff8 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
I guess I'll ignore the LDFLAGS stuff, just brought it up because when I questioned the Arch devs about the new LDFLAGS they mentioned that these were added because most current software should have no problems with the flags used. And now that I look at it, the -Wl is just part of -Wl,--as-needed, so my bad there. On Wed, 2009-09-30 at 09:31 +0200, Lennart Poettering wrote: > On Wed, 30.09.09 15:22, Ng Oon-Ee (ngoo...@gmail.com) wrote: > > > I'm using Archlinux 64-bit (x86_64), and am having trouble compiling > > pulseaudio from git (or even release tarballs) unless CHOST is > > x86_64-unknown-linux-gnu. By default my CHOST is x86_64-pc-linux-gnu. Is > > this an issue with something being hardcoded to the pulse makefiles? > > Easy to work around, though. > > Can you be a bit more elaborate than this? "having trouble" does not > give me the slightest hint what might be going wrong. > > PA itself certainly doesn't check CHOST. Sorry, I was just wondering whether its a known issue. When I try to compile with CHOST=x86_64-pc-linux-gnu, I get errors about undefined reference to `lt__PROGRAM__LTX_preloaded_symbols` in various functions. If you wish the exact error messages I can pastebin it. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
On Wed, 30.09.09 15:22, Ng Oon-Ee (ngoo...@gmail.com) wrote: > I'm using Archlinux 64-bit (x86_64), and am having trouble compiling > pulseaudio from git (or even release tarballs) unless CHOST is > x86_64-unknown-linux-gnu. By default my CHOST is x86_64-pc-linux-gnu. Is > this an issue with something being hardcoded to the pulse makefiles? > Easy to work around, though. Can you be a bit more elaborate than this? "having trouble" does not give me the slightest hint what might be going wrong. PA itself certainly doesn't check CHOST. > On another note, pulse cannot compile when the LDFLAGS --as-needed is > used, should it be able to? Archlinux's default LDFLAGS has just been > updated to use that. Again, easy to work around, but perhaps indicates > some issue with pulse's code? No, --as-needed is a klduge. We explicitly don't support that because there is a cyclic dep between libpulse and libpulsecommon. Try to google or grep the archives for an explanation for that. > ADDITIONAL: on i686, the LDFLAGS -Wl also prevents compiling, though it > doesn't on x86_64... -Wl? what's that supposed to be? I know Wl,--xyz but I never heard of -Wl alone. Also, what's the point? I am pretty sure I can come up with lots of options that make PA fail to build, but why should that matter? For example I am quite sure that CFLAGS=--oh-lets-break-things makes the PA build fail. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Unable to compile for some values of CHOST (on x86_64)
I'm using Archlinux 64-bit (x86_64), and am having trouble compiling pulseaudio from git (or even release tarballs) unless CHOST is x86_64-unknown-linux-gnu. By default my CHOST is x86_64-pc-linux-gnu. Is this an issue with something being hardcoded to the pulse makefiles? Easy to work around, though. On another note, pulse cannot compile when the LDFLAGS --as-needed is used, should it be able to? Archlinux's default LDFLAGS has just been updated to use that. Again, easy to work around, but perhaps indicates some issue with pulse's code? ADDITIONAL: on i686, the LDFLAGS -Wl also prevents compiling, though it doesn't on x86_64... ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
