From: "wezy726" <wezy726@email.msn.com>
To: <gcc-help@gcc.gnu.org>
Subject: Problems Configuring GCC
Date: Mon, 05 Mar 2001 06:37:00 -0000 [thread overview]
Message-ID: <000c01c0a580$ce173c00$3a66193f@0020222191> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
Greetings, all. I am trying to build
gcc-2.95.2 along with a slew of other programming utils in an attempt to make a
"linux from scratch" system. In order to do this, I figured I would try
gcc's ability to make other needed programs if there is a link to them in the
top level gcc src tree. My problem is not with the actual compilation
(yet); the configure script breaks when trying to configure gzip.
Starting from a plain RadHat 7.0 dist, here's what
I did:
Â
Create a suitable directory to install new system
(henceforth called LFS).
Â
Populate LFS with dir structure (/bin, /usr, et
al), basic static binaries (make, gcc-2.96-69(RedHat's latest gcc spin-off),
binutils, texinfo, gawk, sed, grep, flex, fileutils, textutils, shellutils,
bash, bzip2, diffutils), and libraries (glibc-2.2.1 w/ linuxthreads add-on and
linux-2.4.2 w/ crypto patch)
Â
Unpack gcc, gzip, autoconf, automake, bash,
binutils, bison, bzip2, fileutils, findutils, flex, gawk, gettext, grep,
libtool, m4, make, patch, perl, sed, sh-utils, tar, texinfo, and textutils into
LFS/usr/src
Â
Place symbolic links to the directories created in
the gcc-2.95.2 dir. The links are named what they link to sans
version.
i.e. gcc-2.95.2/gzip is a symbolic link to
../gzip-1.2.4a
Â
I then chrooted to LFS, what follows are my command
lines:
Â
mkdir /usr/src/objdir
Â
cd /usr/src/objdir
Â
../gcc*/configure --enable-shared --with-gnu-as
--with-gnu-ld i686-pc-linux-gnu
Â
The configure script runs and, of course, vomits
everything to the screen.
The last three lines before breaking
are:
Â
Configuring gzip...
configure:
gcc-version-trigger=/usr/src/gcc-2.95.2/gcc/version.c: invalid package
name
Configure in /usr/src/objdir/gzip failed,
exiting.
Â
The version.c file (as you probably know) contains
the single line:
Â
char *version_string = "2.95.2 19991024
(release)";
Â
This is where I get stumped... Any insight
into this matter will be greatly appreciated.
Â
PS --Â In case you are wondering, every
program I listed is the latest version from metalab.unc.edu except the RedHat
gcc, but that is not being used after one successful pass through the
compilation process.
Â
PPS -- I realize now that there is a patch
necessary to compile gcc-2.95.2 using glibc-2.2.1 which I hve not applied.Â
However, the system broke before compilation begun so I do not think the patch
is the problem here.
reply other threads:[~2001-03-05 6:37 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='000c01c0a580$ce173c00$3a66193f@0020222191' \
--to=wezy726@email.msn.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).