From: willy@thepuffingroup.com
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] new binutils/gcc
Date: Mon, 14 Feb 2000 23:02:26 -0500 [thread overview]
Message-ID: <20000214230226.P9944@thepuffingroup.com> (raw)
As some of you may have noticed, we now have new binutils and gcc in CVS.
If you previously checked out binutils and/or egcs, you should probably
delete them and get a fresh checkout. Thanks to Cygnus, this is the
ELF-supporting toolchain. Thanks to Sammy, this includes sufficient
support for 32-bit ELF to link a kernel. I've asked him to hold off for
a few days on checking in the kernel changes until everyone has the new
toolchain installed and we have depots/rpms/debs/whatever available.
If you're too impatient or want to hack the toolchain, here's my experience
with it so far on HPUX 11:
install GNU flex. ld won't build with hpux lex, alas.
install GNU bison. gcc doesn't even attempt to use yacc.
cvs co binutils
mkdir binutils-build
cd binutils-build
./binutils/configure --target=hppa1.1-linux --prefix=/home/willy/gcc \
--host=hppa-hpux --disable-nls
make
make install
PATH=/home/willy/gcc/bin:$PATH
cvs co gcc
mkdir gcc-build
cd gcc-build
./gcc/configure --target=hppa1.1-linux --prefix=/home/willy/gcc \
--host=hppa1.1-hpux --disable-nls
make
and then it dies while making libgcc2.a. I'll look at it more tomorrow,
but this may save some people some time.
next reply other threads:[~2000-02-15 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 4:02 willy [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 8:09 [parisc-linux] new binutils/gcc willy
2000-02-25 21:12 ` Paul Bame
2000-02-27 18:26 ` Sam Creasey
2000-02-29 23:06 ` Paul Bame
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=20000214230226.P9944@thepuffingroup.com \
--to=willy@thepuffingroup.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