From: "Paul J.Y. Lahaie" <pjlahaie@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Weird compile problems
Date: Wed, 24 Jan 2001 16:28:13 -0500 [thread overview]
Message-ID: <20010124162813.G19066@achilles.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]
Hello everyone,
I'm in the process of trying to get a working apt (still) and I'm getting
the following with the latest kernel (updated this morning) and the
toolchain from nfsroot-20010118. The system is a C360 with 256MB of RAM.
Compiling deb/debindexfile.cc to /home/pjlahaie/src/apt/build/obj/apt-pkg/debindexfile.opic
deb/debindexfile.cc: In member function `string debSourcesIndex::SourceInfo
(const pkgSrcRecords::Parser &, const pkgSrcRecords::File &) const':
deb/debindexfile.cc:62: Basic block 57 pred edge is corrupted
Predecessor: 14
Successor: 1075043236
deb/debindexfile.cc:62: Basic block 57 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 55 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 53 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 47 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 44 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 41 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 39 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 31 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 28 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 26 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 21 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 19 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 14 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 10 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 7 edge lists are corrupted
deb/debindexfile.cc:62: Basic block 1 edge lists are corrupted
deb/debindexfile.cc:62: Internal compiler error in , at flow.c:6834
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
Now if I do another make, it will compile fine. The file is compiled with
the following options: -g -O -fno-rtti
Is this a kernel problem or a compiler problem? I can move the build
environment over to an A180 instead.
- Paul
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-01-24 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 21:28 Paul J.Y. Lahaie [this message]
2001-01-25 5:58 ` [parisc-linux] Weird compile problems Randolph Chung
[not found] <20010130154256.D6704@achilles.net>
2001-01-30 23:25 ` Alan Modra
2001-01-30 23:36 ` Matt Taggart
2001-01-30 23:45 ` Alan Modra
2001-01-31 1:01 ` Alan Modra
2001-01-31 7:07 ` Alan Modra
2001-02-01 3:59 ` Alan Modra
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=20010124162813.G19066@achilles.net \
--to=pjlahaie@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
/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