public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: PATCH: Re: other/9031
Date: Thu, 26 Dec 2002 14:26:00 -0000	[thread overview]
Message-ID: <20021226222601.11658.qmail@sources.redhat.com> (raw)

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

From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc: dave.anglin@nrc.ca, gcc-patches@gcc.gnu.org, binutils@sources.redhat.com
Subject: PATCH: Re: other/9031
Date: Thu, 26 Dec 2002 17:16:02 -0500 (EST)

 > Thank you very much for your problem report.
 > It has the internal identification `other/9031'.
 > The individual assigned to look at your
 > report is: unassigned. 
 > 
 > >Category:       other
 > >Responsible:    unassigned
 > >Synopsis:       Cygnus configure versus libtool AC_PROG_LD macro
 > >Arrival-Date:   Fri Dec 20 12:36:00 PST 2002
 
 The enclosed patch fixes the problem reported in other/9031.  The technique
 for determining LD is derived from that used by the libtool AC_PROG_LD macro.
 
 Tested on hppa64-hp-hpux11.11 and hppa2.0w-hp-hpux11.11.  Ok for main?
 
 Dave
 -- 
 J. David Anglin                                  dave.anglin@nrc.ca
 National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)
 
 2002-12-26  John David Anglin  <dave.anglin@nrc.ca>
 
 	* configure (LD): Try to set LD to the ld used by gcc when using gcc
 	and not doing a Canadian Cross.
 
 Index: configure
 ===================================================================
 RCS file: /cvsroot/gcc/gcc/configure,v
 retrieving revision 1.50
 diff -u -3 -p -r1.50 configure
 --- configure	16 Dec 2002 18:18:42 -0000	1.50
 +++ configure	21 Dec 2002 21:08:30 -0000
 @@ -1059,6 +1059,29 @@ else
      fi
    fi
  
 +  # If we are using gcc, try to set the LD default to the ld used by gcc.
 +  case "${CC}" in
 +  *gcc)
 +    case $host in
 +    *-*-mingw*)
 +      gcc_prog_ld="`$CC -print-prog-name=ld 2>&1 | tr -d '\015'`" ;;
 +    *)
 +      gcc_prog_ld="`$CC -print-prog-name=ld 2>&1`" ;;
 +    esac
 +    case $gcc_prog_ld in
 +    # Accept absolute paths.
 +    [\\/]* | [A-Za-z]:[\\/]*)
 +      re_direlt='/[^/][^/]*/\.\./'
 +      # Canonicalize the path of ld
 +      gcc_prog_ld=`echo $gcc_prog_ld| sed 's%\\\\%/%g'`
 +      while echo $gcc_prog_ld| grep "$re_direlt" > /dev/null 2>&1; do
 +	gcc_prog_ld=`echo $gcc_prog_ld| sed "s%$re_direlt%/%"`
 +      done
 +      LD="$gcc_prog_ld" ;;
 +    esac
 +    ;;
 +  esac
 +
    CXX=${CXX-"c++"}
    CFLAGS=${CFLAGS-"-g"}
    CXXFLAGS=${CXXFLAGS-"-g -O2"}


             reply	other threads:[~2002-12-26 22:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 14:26 John David Anglin [this message]
2002-12-26 19:16 Alexandre Oliva
2002-12-26 20:16 John David Anglin
2002-12-27 22:26 John David Anglin
2002-12-27 22:36 Alexandre Oliva
2002-12-28  1:26 Alexandre Oliva
2003-01-04 21:06 John David Anglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021226222601.11658.qmail@sources.redhat.com \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).