RE: LDFLAGS

RE: LDFLAGS

[Mansour Al-Aqeel]

Lely
here is the last lines in config.log do they tell you any thing. What
they are telling me is that the 
linker is using that path then, it's going up again to /usr/lib
One more thing to mention, is that the error is generated after it finds
libnewt.a
In other word the rpm package I have on my system doesn't have this
feature or options enabled.
well, I  installed both the library and it's devel package, then I
installed them again from the source
code and when they didn't work I removed it and reinstalled the rpm.
I think i should try the  source installation after enabling these
options. and then we will see.
Do u have any better idea ? 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
configure:958: gcc -E conftest.c
configure:977: checking whether gcc accepts -g
configure:1010: checking for newtInit in -lnewt
configure:1029: gcc -o conftest -g -O2    -static conftest.c -lnewt  
1>&5
/usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libnewt.a(newt.o): In
function `newtFlushInput':
newt.o(.text+0x51): undefined reference to `SLang_getkey'
newt.o(.text+0x5b): undefined reference to `SLang_input_pending'
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
On Mon, 29 Dec 2003 14:07:30 -0700, lrtaylor@micron.com said:
> OK.  Configure is failing.  I didn't realize that that was where you are
> having problems.
> 
> I believe the option for adding a path to the runtime search path is
> -rpath, not -rpath-link, and depending on whether the compiler or ld is
> used to link the program, you would have to specify it differently. 
> However, when you're linking statically, there is no reason to specify a
> runtime search path.
> 
> -Bstatic doesn't cause a problem here, because it doesn't mean the same
> thing.  The -B option tell the compiler where to look for utilities like
> 'as' (the assembler), 'ld' (the linker), etc.  So, what you are really
> telling the compiler with -Bstatic is to look in the directory "static"
> for the linker, assembler, etc.  Not what you meant...
> 
> So, your problem is that the test that configure uses to try to determine
> whether or not libnewt is there is failing.  What you need to do is
> lookin the file config.log to see why that's failing.  Basically, it will
> be the last thing in the log file (although, it may be before a bunch of
> informational junk printed at the end).  Once you're tried to configure
> the program again (using -static instead of -Bstatic, and without the
> -rpath option), and it fails, look at the end of config.log and scroll
> back until you find where the test is failing and see what the actual
> error is there.
> 
> Make sense?
> 
> Cheers,
> Lyle
> 
> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
> Behalf Of Mansour Al-Aqeel
> Sent: Monday, December 29, 2003 1:59 PM
> To: gcc-help@gcc.gnu.org
> Subject: Re: LDFLAGS
> 
> 
> Ok Lyle 
> Here 's the output:
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> checking whether the C compiler (gcc -L/usr/include   -static
> -rpath-link/usr/lib) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for newtInit in -lnewt... no
> configure: error: GNU nparted requires libnewt 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> and that's the command used this time:
>    CFLAGS=-L/usr/include  CPPFLAGS=-L/usr/lib  LDFLAGS=" $LDFLAGS -static
>    -rpath-link/usr/lib" ./configure --prefix=./here
> in my directory: /usr/lib/libnewt.a and  libnewt.so.0.50.35 and their
> links.
> The interesting new thing is that when I use the flag -Bstatic the
> configure doesn't stop ( Funny . right ??)
> make runs and nothing wrong but that's what I get !!!  How and why ??
> That's the magic
> 
> gcc: unrecognized option `-rpath-link/usr/lib'
> gcc: file path prefix `static' never used
> make[1]: Leaving directory `/home/mansour/nparted-0.1'
> 
> and when I give space between  like this  -rpath-link /usr/lib the
> compiler can't generate excutables. :S
> 
> Lyle I can't thank you enough for bearing with me.
> 
> -- 
>   Mansour Al-Aqeel
>   mansour77@ownmail.net
> 
> -- 
> http://www.fastmail.fm - Email service worth paying for. Try it for free
-- 
  Mansour Al-Aqeel
  mansour77@ownmail.net

-- 
http://www.fastmail.fm - Send your email first class

RE: LDFLAGS

[lrtaylor]

OK.  Configure is failing.  I didn't realize that that was where you are having problems.

I believe the option for adding a path to the runtime search path is -rpath, not -rpath-link, and depending on whether the compiler or ld is used to link the program, you would have to specify it differently.  However, when you're linking statically, there is no reason to specify a runtime search path.

-Bstatic doesn't cause a problem here, because it doesn't mean the same thing.  The -B option tell the compiler where to look for utilities like 'as' (the assembler), 'ld' (the linker), etc.  So, what you are really telling the compiler with -Bstatic is to look in the directory "static" for the linker, assembler, etc.  Not what you meant...

So, your problem is that the test that configure uses to try to determine whether or not libnewt is there is failing.  What you need to do is lookin the file config.log to see why that's failing.  Basically, it will be the last thing in the log file (although, it may be before a bunch of informational junk printed at the end).  Once you're tried to configure the program again (using -static instead of -Bstatic, and without the -rpath option), and it fails, look at the end of config.log and scroll back until you find where the test is failing and see what the actual error is there.

Make sense?

Cheers,
Lyle

-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
Behalf Of Mansour Al-Aqeel
Sent: Monday, December 29, 2003 1:59 PM
To: gcc-help@gcc.gnu.org
Subject: Re: LDFLAGS


Ok Lyle 
Here 's the output:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
checking whether the C compiler (gcc -L/usr/include   -static
-rpath-link/usr/lib) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for newtInit in -lnewt... no
configure: error: GNU nparted requires libnewt 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

and that's the command used this time:
   CFLAGS=-L/usr/include  CPPFLAGS=-L/usr/lib  LDFLAGS=" $LDFLAGS -static
   -rpath-link/usr/lib" ./configure --prefix=./here
in my directory: /usr/lib/libnewt.a and  libnewt.so.0.50.35 and their
links.
The interesting new thing is that when I use the flag -Bstatic the
configure doesn't stop ( Funny . right ??)
make runs and nothing wrong but that's what I get !!!  How and why ??
That's the magic

gcc: unrecognized option `-rpath-link/usr/lib'
gcc: file path prefix `static' never used
make[1]: Leaving directory `/home/mansour/nparted-0.1'

and when I give space between  like this  -rpath-link /usr/lib the
compiler can't generate excutables. :S

Lyle I can't thank you enough for bearing with me.

-- 
  Mansour Al-Aqeel
  mansour77@ownmail.net

-- 
http://www.fastmail.fm - Email service worth paying for. Try it for free

Re: LDFLAGS

[Mansour Al-Aqeel]

Ok Lyle 
Here 's the output:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
checking whether the C compiler (gcc -L/usr/include   -static
-rpath-link/usr/lib) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for newtInit in -lnewt... no
configure: error: GNU nparted requires libnewt 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

and that's the command used this time:
   CFLAGS=-L/usr/include  CPPFLAGS=-L/usr/lib  LDFLAGS=" $LDFLAGS -static
   -rpath-link/usr/lib" ./configure --prefix=./here
in my directory: /usr/lib/libnewt.a and  libnewt.so.0.50.35 and their
links.
The interesting new thing is that when I use the flag -Bstatic the
configure doesn't stop ( Funny . right ??)
make runs and nothing wrong but that's what I get !!!  How and why ??
That's the magic

gcc: unrecognized option `-rpath-link/usr/lib'
gcc: file path prefix `static' never used
make[1]: Leaving directory `/home/mansour/nparted-0.1'

and when I give space between  like this  -rpath-link /usr/lib the
compiler can't generate excutables. :S

Lyle I can't thank you enough for bearing with me.

-- 
  Mansour Al-Aqeel
  mansour77@ownmail.net

-- 
http://www.fastmail.fm - Email service worth paying for. Try it for free