This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/1512: Path confusion w/ -print-prog-name + autoconf
- To: gcc-gnats at gcc dot gnu dot org
- Subject: other/1512: Path confusion w/ -print-prog-name + autoconf
- From: nneul at umr dot edu
- Date: 26 Dec 2000 21:16:53 -0000
- Reply-To: nneul at umr dot edu
>Number: 1512
>Category: other
>Synopsis: Path confusion w/ -print-prog-name + autoconf
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Dec 26 13:26:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: nneul@umr.edu
>Release: current cvs as of 12/20 and older
>Organization:
>Environment:
anything, but gcc accessed via symbolic link tree
>Description:
infinity(251)>gcc -print-prog-name=ld
/umr/devbin/../lib/gcc-lib/i686-pc-linux-gnu/2.97/../../../../i686-pc-linux-gnu/bin/ld
autoconf:
checking for ld used by GCC... (cached) /umr/i686-pc-linux-gnu/bin/ld
checking if the linker (/umr/i686-pc-linux-gnu/bin/ld) is GNU ld... (cached) no
That's a problem. It seems to me it's an autoconf issue really,
but is there any way to change the specs file/build process/etc. to
get gcc to return a more reasonable path for the path to ld?
Accessing the ld via the gcc generated path is valid, but it
requires the ..'s. It appears that autoconf flattens it, but flattens it by
removing the ..'s and paired dir.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: