From: willy@thepuffingroup.com
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] new binutils/gcc
Date: Tue, 15 Feb 2000 03:09:46 -0500 [thread overview]
Message-ID: <20000215030946.V9944@thepuffingroup.com> (raw)
ok, I couldn't wait till tomorrow..
You'll need an include directory. You can either do it the way I did
(pick them out of glibc, one at a time), or you can get a tarball of
the fruits of my labour:
ftp://puffin.external.hp.com/pub/parisc/src/include.tar.gz
Plop this into your $prefix after installing binutils. ie this was the
contents of /home/willy/gcc/include. Now you need to persuade gcc to look
there for it (I thought it was supposed to do that automatically, but it seems
not). Change line 370 of gcc-build/gcc/Makefile to read:
LIBGCC2_INCLUDES = -I/home/willy/gcc/include
and then type make. Now I get to :
Testing libgcc1. Ignore linker warning messages.
/home/willy/cvs/gcc-build/gcc/xgcc -B/home/willy/cvs/gcc-build/gcc/ \
-B/home/willy/gcc/hppa1.1-linux/bin/ \
-I/home/willy/gcc/hppa1.1-linux/include -DCROSS_COMPILE -DIN_GCC \
-DMULTIBYTE_CHARS=1 -g -O2 -I./include libgcc1-test.o \
-o libgcc1-test \
-nostartfiles -nostdlib `/home/willy/cvs/gcc-build/gcc/xgcc \
-B/home/willy/cvs/gcc-build/gcc/ -B/home/willy/gcc/hppa1.1-linux/bin/ \
-I/home/willy/gcc/hppa1.1-linux/include --print-libgcc-file-name`
/home/willy/gcc/hppa1.1-linux/bin/ld: can not size stub section: Bad value
libgcc1-test.o: In function `main_without__main':
/home/willy/cvs/gcc-build/gcc/../../gcc/gcc/libgcc1-test.c:20: undefined reference to `$$divI'
/home/willy/cvs/gcc-build/gcc/../../gcc/gcc/libgcc1-test.c:14: undefined reference to `$global$'
death: $$divI type 1
collect2: ld returned 1 exit status
make[1]: *** [libgcc1-test] Error 1
(wrapped for better mailer handling)
And with that I really am going to bed. g'night.
next reply other threads:[~2000-02-15 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 8:09 willy [this message]
2000-02-25 21:12 ` [parisc-linux] new binutils/gcc Paul Bame
2000-02-27 18:26 ` Sam Creasey
2000-02-29 23:06 ` Paul Bame
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 4:02 willy
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=20000215030946.V9944@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