public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gml4410@ggr.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: other/8644: make install fails, as it is trying to build things
Date: Tue, 26 Nov 2002 12:26:00 -0000	[thread overview]
Message-ID: <20021119193323.28967.qmail@sources.redhat.com> (raw)


>Number:         8644
>Category:       other
>Synopsis:       make install fails, as it is trying to build things
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 19 11:36:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gordon Lack
>Release:        gcc 3.2
>Organization:
>Environment:
SGI Irx 6.5
>Description:
   I have various SGI Irix systems - some with 32 and some with 64-bit OSes.

   These mount their tools from an NFS server.

   We have a development system which is a 64-bit system. Tools are
installed from 32-bit workstations.

   I have compiled gcc 3.2 (make bootstrap) on the 64-bit server.  This
seems OK.

   I now wish to install this using a 32-bit system (which is the only
system with write access to the NFS file system).

   However, "make install" doesn't just install, it tries to rebuild
mabi=64/libgcc_s.so.1, which is 64-bit library.  The 32-bit system does
not have libc installed for this, so the linking fails and with it the
installation.

   The problem appears to be in the libgcc.mk file.  A node exists for:

mabi$(EQ)64/libgcc_s_mabi$(EQ)64.so:

(where $(EQ) is = ).  However, the rule for this actually uses xgcc to
build mabi=64/libgcc_s.so.1 followed by:

 rm -f libgcc_s_mabi=64.so 
 ln -s mabi=64/libgcc_s.so.1 libgcc_s_mabi=64.so

so the node isn't actually built by the rule!  These last two lines
would seem to need to be:

 rm -f mabi=64/libgcc_s_mabi=64.so
 ln -s libgcc_s.so.1 mabi=64/libgcc_s_mabi=64.so

in order to fit in with this and other rules.


   Mind you, even after that I have problems as the install wishes to
echo timestamp to stmp-multilib, even though it already exists and is up
to date.  Since this is from an NFS mounted disk and I;m installign as
root it fails...
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-11-19 19:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021119193323.28967.qmail@sources.redhat.com \
    --to=gml4410@ggr.co.uk \
    --cc=gcc-gnats@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).