From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: joel.soete@freebel.net
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.2 experimental debs
Date: Tue, 23 Apr 2002 17:47:58 -0400 [thread overview]
Message-ID: <20020423174758.C8545@systemhalted> (raw)
In-Reply-To: <1019582168.3cc596d87ba8a@webmail.tiscalinet.be>; from joel.soete@freebel.net on Tue, Apr 23, 2002 at 07:16:08PM +0200
>
> Joel
>
> PS1: about step 4.2 of your howto-xc, I notice a small difference between html
> and pdf (in html you use gcc option "enable-shared" in pdf "disable-shared").
> But this not the cause of the above problem.
>
> PS2: I also make an apt-get dist-upgrade (with ftp.de.debian.org) so that native
> gcc is now 3.0.4-5 (I think it was already installed last week)
>
>
Both the HTML and PDF version are the same (just double checked).
http://www.baldric.uwo.ca/~carlos/HOWTO-Parisc/index.html
http://www.baldric.uwo.ca/~carlos/HOWTO-Parisc/HOWTO-Building_PARISC-LINUX_CrossCompiler.pdf
In section 4.2 you are bootstraping the C compiler without glibc
so you must use --disable-shared.
In section 4.5 you have already built glibc and you can turn
shared support back on with --enable-shared.
c.
p.s. The HTML and PDF do have some formatting differences...
I'll get around to making them look similar later :}
Dang... just noticed I missed one of the path changes in
the pdf...
next prev parent reply other threads:[~2002-04-23 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 13:05 [parisc-linux] gcc-3.2 experimental debs Joel Soete
2002-04-21 15:25 ` Matthew Wilcox
2002-04-23 15:19 ` Carlos O'Donell Jr.
2002-04-23 17:16 ` joel.soete
2002-04-23 17:24 ` John David Anglin
2002-04-23 21:47 ` Carlos O'Donell Jr. [this message]
2002-04-24 13:42 ` joel.soete
2002-04-24 13:50 ` joel.soete
2002-04-21 15:53 ` Randolph Chung
2002-04-22 6:18 ` joel.soete
-- strict thread matches above, loose matches on Subject: below --
2002-04-19 22:16 Randolph Chung
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=20020423174758.C8545@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=joel.soete@freebel.net \
--cc=parisc-linux@lists.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.