| 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: Karl Lindén <spray.sucks@xxxxxxxxx>
- Date: Mon, 1 Apr 2013 19:24:09 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=aKaqS2pDAt6a1IsQYYD44iXue0xAf9rI33lf+dgx2Ng=; b=g+v/TnsiLsNkdsCINiZ8w3kLMxyRLAydoc4E0vK1QO7U92u00SX8/XdfLlRF5TvBb6 kHQRh5b+rg11mgGicNuPKQYRzvCjEL0eB5YJYzUXCGW8yr2IvVhIvlI13VrHP+fziHkh rfJSNubYq0cGcz7W4+riilEFwsJTaOAsBm0pH2kw+Y/2hJ0nfEVm4ewSqzL3up2WAfdn 2KGSmQvjABxJvi3iBj62hztdL00yWxBhmmpQaQ3flldR0wKeEZTD8mdyk+ls7lktmpQ6 gdDH9K5X1Ssj6E/mUuklIorRfoFHwkcKMBXo53hQ1mZLLO0YRCMkaVp0Iy9WMx/57U/l 6yNg==
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."
>
>