public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: roy@panix.com To: gcc-gnats@gcc.gnu.org Subject: bootstrap/10289: config.status contains incorrect information Date: Tue, 01 Apr 2003 21:46:00 -0000 [thread overview] Message-ID: <20030401213605.4821.qmail@sources.redhat.com> (raw) >Number: 10289 >Category: bootstrap >Synopsis: config.status contains incorrect information >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 01 21:46:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: roy@panix.com >Release: gcc-3.2.2 >Organization: >Environment: RedHat-6.2 >Description: I unpacked gcc-3.2.2.tar.gz, created a obj directory, cd'd to that directory, and ran ../gcc-3.2.2/configure. This resulted in the attached config.status file. The problem is, if I make a new build object directory, and rerun the full command indicated in the config.status file, I end up with an unusable object directory -- there's no gcc subdirectory, for example. Running configure with no arguments results in a correct object directory being built. >How-To-Repeat: tar xvzf gcc-3.2.2.tar.gz mkdir build cd build ../gcc-3.2.2/configure cd .. mkdir build2 cd build2 ../build/config.status ls -l notice that there's no gcc directory in build2, like there was in build. This causes "make bootstrap" to fail when it tries to cd to gcc. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="config.status" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="config.status" IyEvYmluL3NoCiMgVGhpcyBmaWxlIHdhcyBnZW5lcmF0ZWQgYXV0b21hdGljYWxseSBieSBjb25m aWd1cmUuICBEbyBub3QgZWRpdC4KIyBUaGlzIGRpcmVjdG9yeSB3YXMgY29uZmlndXJlZCBhcyBm b2xsb3dzOgouLi9nY2MtMy4yLjIvY29uZmlndXJlIC0td2l0aC1nY2MtdmVyc2lvbi10cmlnZ2Vy PS9ob21lL3JzbWl0aC9nY2MvZ2NjLTMuMi4yL2djYy92ZXJzaW9uLmMgLS1ob3N0PWk2ODYtcGMt bGludXgtZ251IC0tbm9yZWN1cnNpb24gCiMgIHVzaW5nICJtdC1mcmFnIgo=
next reply other threads:[~2003-04-01 21:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-01 21:46 roy [this message] 2003-04-10 14:29 ebotcazou
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=20030401213605.4821.qmail@sources.redhat.com \ --to=roy@panix.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: linkBe 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).