Re: bootstrap/7323: Install failed to property account for libstdc++ location

Re: bootstrap/7323: Install failed to property account for libstdc++ location

[Dara Hazeghi]

The following reply was made to PR bootstrap/7323; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, anamax@earthlink.net, nobody@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location
Date: Wed, 14 May 2003 02:16:33 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=7323
 
 Hello,
 
 does the submitter still consider the reported behavior a bug? If so, I  
 guess we can update the documentation... Thanks,
 
 Dara
 

Re: bootstrap/7323: Install failed to property account for libstdc++ location

[giovannibajo]

Synopsis: Install failed to property account for libstdc++ location

State-Changed-From-To: open->feedback
State-Changed-By: bajo
State-Changed-When: Wed May 14 10:53:12 2003
State-Changed-Why:
    See Dara's question.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7323

Re: bootstrap/7323: Install failed to property account for libstdc++ location

[Andy Freeman]

The following reply was made to PR bootstrap/7323; it has been noted by GNATS.

From: "Andy Freeman" <anamax@earthlink.net>
To: "Andrew Pinski" <pinskia@physics.uc.edu>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location
Date: Mon, 15 Jul 2002 22:52:12 -0700

 Huh?
 
 I suspect g++/ld knew where the correct library was when they generated
 the executable, so why isn't that info in the executable for startup?  Why
 is it a good thing that it isn't?
 
 In other words, are you saying that I have to set LD_LIBRARY_PATH
 correctly before I start each executable....  (There are at least two ways
 to end up with different libraries that have the same base name+extension,
 so if the lookup is by file base name+extension, there's no way to have a
 single LD_LIBRARY_PATH that is always correct at startup.)
 
 -andy
 
 
 ----- Original Message ----- 
 From: "Andrew Pinski" <pinskia@physics.uc.edu>
 To: <anamax@earthlink.net>
 Cc: <gcc-gnats@gcc.gnu.org>
 Sent: Monday, July 15, 2002 9:40 PM
 Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location
 
 
 > The fix is really to set LD_LIBRARY_PATH to include your prefix:
 > /home/andy/GCC3.1/gcc-3.1-bin.
 > 
 > This is because gcc now uses shared libraries and you did not
 > install gcc where ld*.so find them.
 > 
 > Thanks,
 > Andrew Pinski
 > 
 

Re: bootstrap/7323: Install failed to property account for libstdc++ location

[Andrew Pinski]

The following reply was made to PR bootstrap/7323; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: anamax@earthlink.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location
Date: Tue, 16 Jul 2002 00:40:28 -0400

 The fix is really to set LD_LIBRARY_PATH to include your prefix:
 	/home/andy/GCC3.1/gcc-3.1-bin.
 
 This is because gcc now uses shared libraries and you did not
 install gcc where ld*.so find them.
 
 Thanks,
 Andrew Pinski
 

bootstrap/7323: Install failed to property account for libstdc++ location

[anamax]

>Number:         7323
>Category:       bootstrap
>Synopsis:       Install failed to property account for libstdc++ location
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 15 21:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Andy Freeman
>Release:        unknown-1.0
>Organization:
>Environment:
x86 redhat 7.3
>Description:
If one configures, builds, and installs GCC/g++ as described by the gcc -v output attached, the executable doesn't know where to find libstdc++.so.4 (as a shared library) on startup.
>How-To-Repeat:
configure, build, and install as noted.  Compile a c++ program.  Try to run it.
>Fix:
Can workaround by using -static 
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="specs.txt"
Content-Disposition: inline; filename="specs.txt"

Reading specs from gcc-3.1-bin/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../gcc-3.1/configure --prefix=/home/andy/GCC3.1/gcc-3.1-bin --with-local-prefix=/home/andy/GCC3.1/gcc-3.1-include --program-suffix=3.1 --enable-threads=posix --enable-version-specific-runtime-libs --enable-languages=c++
Thread model: posix
gcc version 3.1