| Re: [proaudio] strange 1 april bug |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] strange 1 april bug
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Mon, 1 Apr 2013 19:40:38 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Mon, 1 Apr 2013 19:24:09 +0200,
Karl Lindén <spray.sucks@xxxxxxxxx> 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.
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 <dominique.michel@xxxxxxxxx>:
> > 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."