public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Robert W. Hasker" <hasker@baobab.cs.uwplatt.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/7555: make command too long during install for gcc-3.1.1 on alpha axp
Date: Tue, 20 May 2003 02:06:00 -0000	[thread overview]
Message-ID: <20030520020603.4780.qmail@sources.redhat.com> (raw)

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

From: "Robert W. Hasker" <hasker@baobab.cs.uwplatt.edu>
To: dhazeghi@yahoo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/7555: make command too long during install for gcc-3.1.1
 on alpha axp
Date: Mon, 19 May 2003 21:01:53 -0500 (CDT)

    sorry for the repeat mailing, but could the submitter of this PR also  
    verify whether this is still a problem with current gcc releases?
 
 It is still a problem with version 3.2.3.  When I try to build into the
 directory 
 
         /usr2/sys/usr/local/src/gcc/build323
 
 "make install" fails with the error
 
 if [ -z "" ]; then  true;  else  rootpre=`pwd`/; export rootpre;  srcrootpre=`cd ../../../gcc-3.2.3/libiberty; pwd`/; export srcrootpre;  lib=`echo ${rootpre} | sed -e 's,^.*/\([^/][^/]*\)/$,\1,'`;  compiler="/usr2/sys/usr/local/src/gcc/build323/gcc/xgcc -B/usr2/sys/usr/local/src/gcc/build323/gcc/ -B/usr/local/alpha-dec-osf4.0g/bin/ -B/usr/local/alpha-dec-osf4.0g/lib/ -isystem /usr/local/alpha-dec-osf4.0g/include";  for i in `${compiler} --print-multi-lib 2>/dev/null`; do  dir=`echo $i | sed -e 's/;.*$//'` ;  if [ "${dir}" = "." ]; then  true;  else  if [ -d ../${dir}/${lib} ]; then  flags=`echo $i | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`;  if (cd ../${dir}/${lib}; make "AR=ar"  "AR_FLAGS=rc"  "CC=/usr2/sys/usr/local/src/gcc/build323/gcc/xgcc -B/usr2/sys/usr/local/src/gcc/build323/gcc/ -B/usr/local/alpha-dec-osf4.0g/bin/ -B/usr/local/alpha-dec-osf4.0g/lib/ -isystem /usr/local/alpha-dec-osf4.0g/include"  "CFLAGS=-g -O2"  "DESTDIR="  "LIBCFLAGS=-g -O2"  "EXTRA_OFILES="  "HDEFINES=" !
  "INSTALL=/bin/sh /usr2/sys/usr/local/src/gcc/gcc-3.2.3/install-sh -c"  "INSTALL_DATA=/bin/sh /usr2/sys/usr/local/src/gcc/gcc-3.2.3/install-sh -c -m 644"  "INSTALL_PROGRAM=/bin/sh /usr2/sys/usr/local/src/gcc/gcc-3.2.3/install-sh -c "  "LDFLAGS="  "LOADLIBES="  "RANLIB=ranlib"  "SHELL=/bin/sh"  "prefix=/usr/local"  "exec_prefix=/usr/local"  "libdir=/usr/local/lib"  "libsubdir=/usr/local/lib/gcc-lib/alpha-dec-osf4.0g/3.2.3"  "tooldir=/usr/local/alpha-dec-osf4.0g"  CFLAGS="-g -O2 ${flags}"  prefix="/usr/local "  exec_prefix="/usr/local"  GCJFLAGS=" ${flags}"  CXXFLAGS="-g -O2 ${flags}"  LIBCFLAGS="-g -O2 ${flags}"  LIBCXXFLAGS="-g -O2 -fno-implicit-templates ${flags}"  LDFLAGS=" ${flags}"  DESTDIR=""  install); then  true;  else  exit 1;  fi;  else true;  fi;  fi;  done;  fi
 Make: line too long.  Stop.
 *** Exit 1
 Stop.
 
 Building into /usr2/sys/usr/local/src/b works, however.
 
 Rob


             reply	other threads:[~2003-05-20  2:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  2:06 Robert W. Hasker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 10:42 giovannibajo
2003-05-08  4:36 Dara Hazeghi
2002-08-09  8:46 Robert W. Hasker

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=20030520020603.4780.qmail@sources.redhat.com \
    --to=hasker@baobab.cs.uwplatt.edu \
    --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).