Armin K. wrote:
On 11/02/2014 11:06 PM, Guy Dalziel wrote:
I thought I would post this in case anyone finds it useful. It's not a problem
with the compilation instructions, but rather the way I set up my environment.
When I started to compile Xorg I started compiling the protocol headers, and the
first one that it tried to compile threw back this:
checking whether the C compiler works... no
configure: error: in
`/home/krendoshazin/src/packages/xc/proto/bigreqsproto-1.1.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
Checking config.log showed me 'gcc: error: ./specs: Is a directory'. It seems
that GCC was reacting to the presence of the specs directory and expecting it to
be a file.
After a bit of digging it turns out that the problem is the LIBRARY_PATH
variable as I'd set up my bash environment to set this up for me by default with
LIBRARY_PATH=$LIBRARY_PATH:$XORG_PREFIX/lib. This is necessary for when Xorg is
built in a directory other than /usr as I do.
I tend to use append instead of prepend, so it goes: export
LD_LIBRARY_PATH=$XORG_PREFIX/lib:$LD_LIBRARY_PATH. Even if
LD_LIBRARY_PATH was empty, nothing will get broken that way.
Or you could just use the pathappend() or pathprepend() bash functions
in the BLFS section 'The Bash Shell Startup Files'.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
