Hmm, I think the best is to do both and providing a link to each other on the both trackers just for the reference.
2013/4/1 Dominique Michel <[email protected]>: > Le Mon, 1 Apr 2013 19:40:38 +0200, > Dominique Michel <[email protected]> a écrit : > >> Le Mon, 1 Apr 2013 19:24:09 +0200, >> Karl Lindén <[email protected]> a écrit : >> >> This is the portage default ldflags: "-Wl,-O1 -Wl,--as-needed" >> I don't even define them in make.conf. Without them, it work, with >> them, it fail. > > This is the -Wl,--as-needed that cause the failure. > >> >> Should I report the bug upstream, or the gentoo too? >> >> Dominique >> >> > Hi, >> > >> > I have had a similar issue when writing my own software. I get such >> > behaviour with the -Werror CFLAG; if it is given the test fails and >> > if not it succeeds. I think it can be something similar here. >> > However, I assume you have not set -Werror in your CFLAGS, so it >> > could be bound to another flag. Have you tried a manual >> > configuration with your portage CFLAGS or differing the build >> > environment to be more like the one in portage? >> > >> > You should probably report the bug, even if you solve the issue. >> > Just so it is known. >> > >> > Regards, >> > Karl >> > >> > 2013/4/1 Dominique Michel <[email protected]>: >> > > That's not a first april joke, I really get a very strange portage >> > > behaviour. >> > > >> > > emerge aj-snapshot >> > > ... >> > > ./configure --prefix=/usr --build=x86_64-pc-linux-gnu >> > > --host=x86_64-pc-linux-gnu --mandir=/usr/share/man >> > > --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc >> > > --localstatedir=/var/lib --libdir=/usr/lib64 >> > > ... >> > > checking mxml.h usability... yes >> > > checking mxml.h presence... yes >> > > checking for mxml.h... yes >> > > checking for main in -lasound... yes >> > > checking for main in -ljack... yes >> > > checking for mxmlLoadFile in -lmxml... no >> > > configure: error: mxml library (mxml) is required >> > > >> > > If I go in $WORKDIR and issue exactly the same configure command, >> > > or just ./configure, it just work and I can compile the software. >> > > >> > > I also get this strange f. bug in my 2 machines. >> > > Any clue? Or is it a portage bug that must be reported? >> > > >> > > Dominique >> > > >> > > -- >> > > "We have the heroes we deserve." >> > > >> > > >> > >> > >> >> > > > -- > "We have the heroes we deserve." > >
