From: Paul Bame <bame@endor.fc.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] building a glibc-based tool chain
Date: Thu, 13 Apr 2000 17:38:31 -0600 [thread overview]
Message-ID: <E12ftBw-0003b1-00@endor.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 11 Apr 2000 09:50:55 MDT." <E12f2wJ-0002l4-00@endor.fc.hp.com>
Ok, using my prior instructions you'll get a 'glibc' containing
x86 object files! crt1.o is one of those, and is probably why the
linker segfaults.
Although this is still naive, a better glibc config command is:
.../configure \
--prefix=/opt/palinux/lib/gcc-lib/hppa1.1-linux/2.9-hppa-991112 \
--disable-nls \
--disable-sanity-checks \
--disable-shared \
--host=hppa1.1-linux \
--target=hppa1.1-linux \
--build=i386-linux \
--with-headers=/opt/puffin/include \
--without-nls \
--disable-profile
Currently this is dying in the glibc build but that will probably get
fixed tomorrow.
-P
next prev parent reply other threads:[~2000-04-13 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 18:05 [parisc-linux] building a glibc-based tool chain Paul Bame
2000-04-09 6:06 ` Bdale Garbee
2000-04-09 7:27 ` Bdale Garbee
2000-04-09 16:17 ` David Huggins-Daines
2000-04-09 16:56 ` Bdale Garbee
2000-04-11 15:50 ` Paul Bame
2000-04-13 23:38 ` Paul Bame [this message]
2000-04-14 21:48 ` David Huggins-Daines
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=E12ftBw-0003b1-00@endor.fc.hp.com \
--to=bame@endor.fc.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.