public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mat_geek@yahoo.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/6776: Build 3.1 Source - Build directory on another file system fails due to hard link creation.
Date: Wed, 22 May 2002 18:06:00 -0000 [thread overview]
Message-ID: <20020523010515.5269.qmail@sources.redhat.com> (raw)
>Number: 6776
>Category: libstdc++
>Synopsis: Build 3.1 Source - Build directory on another file system fails due to hard link creation.
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed May 22 18:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: mat_geek@yahoo.com
>Release: 3.1
>Organization:
>Environment:
Linux, Redhat 7.0. GCC 3.0. Ext2 (/) file system. FAT 16 (/mnt/data) file system.
>Description:
Building LibSTDC++ fails if the build directory is not in the same file system as the source directory.
>How-To-Repeat:
Install source code on one file system, or file system that doesn't support hard links, and create the build directory on another file system, or the same one if it doesn't support hard links.
Configure and 'make bootstrap'. The build progresses fine until the LibSTDC++ make where it attempts to create a hard link from a header in /usr/local/include on Ext2 to LibSTDC++'s "src/base_stdio.h" in build directory on FAT16.
>Fix:
Change the make file to handle the linking failure and do a copy instead.
I tried to copy the file manually but the make file still tries to create the hard link.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-05-23 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:06 mat_geek [this message]
2002-05-23 8:42 bkoz
2002-06-04 0:16 Matthew Hounsel
2002-08-03 13:21 bkoz
2003-02-23 20:31 neroden
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=20020523010515.5269.qmail@sources.redhat.com \
--to=mat_geek@yahoo.com \
--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).