discuss-gnustep
[Top][All Lists]
Advanced

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

Re: Compiling on openbsd with gcc4.8, executables fail to run


From: Riccardo Mottola
Subject: Re: Compiling on openbsd with gcc4.8, executables fail to run
Date: Tue, 07 Jan 2014 02:00:15 +0100
User-agent: Mozilla/5.0 (X11; OpenBSD i386; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19

Wolfgang Lux wrote:
Am 02.01.2014 um 09:26 schrieb Riccardo Mottola:

Hi,

Wolfgang Lux wrote:
You'd fix this in one of the usual ways when your library search path is wrong. 
You might try adding /usr/local/iib to (the end of) your LD_LIBRARY_PATH 
environment variable. Or you might add -Wl,-R/usr/local/lib to LDFLAGS when 
configuring gnustep-make.
this works!

However, I have to append CC, CXX and LDFLAGS for every "configure" (not only 
core, but also gworkspace)
If I only need to type "make" and it is a standard gnustep-make, instead, it 
works.

I wonder if that can be improved? I suppose it is a configure shortcoming.
The problem is that the configure scripts do not know about any variables set 
during the configuration of gnustep-make. This could be avoided by using 
something like CC=`gnustep-config --variable=CC` for the compiler programs. In 
fact, the configure script for gnustep-base already contains such code for some 
time. However, these assignments didn't make their way into other gnustep 
libraries or applications. In addition, this trick does not work for CFLAGS or 
LDFLAGS, since gnustep-config does not offer to return their values.
Ah, interesting. I think it would make sense, doesn't it?
Candidates would be CC and CXX, but also CFLAGS and LDFLAGS.

I should perhaps copy that CC part into gworkspace and other configure runnig stuff, I didn't know about it

Nicola, are you reading? :)

Riccardo




reply via email to

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