From: joel.soete@freebel.net
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: joel.soete@freebel.net, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.2 bootstrap?
Date: Tue, 16 Jul 2002 18:03:29 +0200 (CEST) [thread overview]
Message-ID: <1026835409.3d3443d1d1cbd@webmail.tiscalinet.be> (raw)
In-Reply-To: <200207161516.g6GFGZ8C023053@hiauly1.hia.nrc.ca>
Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:
>
> Possibilities are:
>
> 1) you either didn't install what you built.
> 2) you moved stuff around so libgcc couldn't be found.
> 3) libgcc.a didn't build when you built your cross.
> 4) linker script didn't link in libgcc.a.
>
> $$mulU is a millicode routine in libgcc.a.
Humm?
In the debian package gcc-3.0 I found this lib and
strings /usr/lib/gcc-lib/hppa-linux/3.0.4/libgcc.a | grep mulU
show me well two entries.
but in ./native/lib/gcc-lib/hppa-linux/3.2 (as well in ./cross) I do not found
anything like this.
So this is a 5th possibility: the procedure used failled to build correctly this
lib (at least?)
>
> > Or would it be better to continue with xcompiler hppa->hppa?
>
> You are just adding more complication to the process trying to use
> ia64.
Oops I wrongly explain (sorry for confusion): I do not use ia64, I just use this
procedure as a model.
I change just enough to run it on my hppa-linux box (a b2000 here) but without
success :(. I still have a lot to learn.
Thanks for info,
Joel
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next prev parent reply other threads:[~2002-07-16 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 15:04 [parisc-linux] gcc-3.2 bootstrap? joel.soete
2002-07-16 15:16 ` John David Anglin
2002-07-16 16:03 ` joel.soete [this message]
2002-07-16 16:13 ` Randolph Chung
2002-07-16 16:39 ` joel.soete
[not found] <no.id>
2002-07-16 17:27 ` John David Anglin
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=1026835409.3d3443d1d1cbd@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@parisc-linux.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 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.