From: "J.D. Bronson" <jd@wixb.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: 3.4.0 on solaris fails on install
Date: Wed, 21 Apr 2004 23:31:00 -0000 [thread overview]
Message-ID: <6.1.0.6.2.20040421183026.00be6ca8@cheyenne.wixb.com> (raw)
In-Reply-To: <orsmexx82o.fsf@free.redhat.lsd.ic.unicamp.br>
At 05:46 PM 4/21/2004, Alexandre Oliva wrote:
>On Apr 21, 2004, "J.D. Bronson" <jd@wixb.com> wrote:
>
> > I used a precompild gcc 2.95.3 and build gcc 3.4.0 just fine.
> > However the install fails!
>
>Ugh. INSTALL_PROGRAM is passed from the top level to all subdirs, so
>it doesn't work when srcdir is relative. I suspect this is why we say
>we don't support objdir as a subdir of srcdir in the installation
>documentation: people will tend to use relative pathnames for that.
>
>I suppose it will work if you run
>
>make install INSTALL_PROGRAM=/full/path/to/src/install-sh
>
>Please file a bug report on this, such that this doesn't get lost. At
>the very least, the documentation should be changed to make it clear
>that relative pathnames are not expected to work.
>
>Thanks,
>
>--
>Alexandre Oliva http://www.ic.unicamp.br/~oliva/
I will try this. However, I never had any issues until just now.
Usually I do this :
unzip gcc into /junk
cd /junk/gcc*
mkdir obj
cd obj
../configure BLAH
make bootstrap
make install
isnt that that the normal and recommended way?
..I tried this same way (above) on my FreeBSD 5.2.1 system and it built
100% fine. So could this be a solaris issue? - I am running solaris10 beta...
--
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282
next prev parent reply other threads:[~2004-04-21 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 22:06 J.D. Bronson
2004-04-21 22:47 ` Alexandre Oliva
2004-04-21 23:31 ` J.D. Bronson [this message]
2004-04-21 23:36 lrtaylor
[not found] ` <363801FFD7B74240A329CEC3F7FE4CC4015F3C6C@ntxboimbx07.micro n.com>
2004-04-21 23:43 ` J.D. Bronson
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=6.1.0.6.2.20040421183026.00be6ca8@cheyenne.wixb.com \
--to=jd@wixb.com \
--cc=aoliva@redhat.com \
--cc=gcc-help@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).