hydra-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: i686-solaris


From: Vincent Lefevre
Subject: Re: i686-solaris
Date: Fri, 12 Jul 2013 12:31:57 +0200
User-agent: Mutt/1.5.21-6305-vl-r59709 (2013-04-16)

On 2013-07-12 11:55:50 +0200, Vincent Lefevre wrote:
> On 2013-07-12 11:15:15 +0200, Ludovic Courtès wrote:
> > Vincent Lefevre <address@hidden> skribis:
> > > On 2013-07-12 09:25:59 +0200, Zimmermann Paul wrote:
> [...]
> > >> configure:15350: gcc -std=gnu99 -o conftest -Wall -Wmissing-prototypes 
> > >> -Wpointer-arith -m32 -O2 -pedantic -fomit-frame-pointer -mtune=pentium2 
> > >> -march=pentium2 -ffloat-store 
> > >> -I/nix/store/yz4r78ssvhz4cc0xj4z9mv98m2xz9q97-gmp-4.3.2/include 
> > >> -L/nix/store/yz4r78ssvhz4cc0xj4z9mv98m2xz9q97-gmp-4.3.2/lib conftest.c 
> > >> -lgmp  >&5
> > >> configure:15350: $? = 0
> > >> configure:15350: ./conftest
> > >> gmp.h: 4.3.2 / libgmp: 4.3.1
> [...]
> > > It would be surprising to have a wrong GMP installation. I have the
> > > impression that libgmp 4.3.1 comes from a system-wide installation,
> > > e.g. /usr/lib,
> > 
> > Yes, but we provide explicit -I and -L flags pointing to 4.3.2 (see
> > above; this comes from mpfr/release.nix.)
> 
> I thought they came from --prefix (in which case the problem would not
> be specific to Hydra), but there may be something hidden in the logs.

Indeed one can see later that CPPFLAGS and LDFLAGS are used.

> > However, it may be that ./conftest above is picking /usr/lib/libgmp.so
> > at run time, presumably because /nix/store/...-gmp-4.3.2/lib is not in
> > the loader’s search path.  Nixpkgs’s ld-wrapper normally adds it to the
> > RPATH [0], but perhaps this has lower precedence than /usr/lib?
> 
> It didn't: there's no trace of -rpath in the above gcc line.
> 
> And $LD_RUN_PATH was not predefined either. MPFR's configure does:
[...]

I've done a test on a Solaris machine, and providing LD_RUN_PATH in
addition to CPPFLAGS and LDFLAGS works.

The drawback of LD_RUN_PATH is that it may affect other programs run
in the build. I wonder whether there's a portable way to avoid it.

-- 
Vincent Lefèvre <address@hidden> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]