From: joel.soete@freebel.net
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: joel.soete@freebel.net, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] GCC support for dwarf2
Date: Fri, 12 Apr 2002 18:37:56 +0200 (CEST) [thread overview]
Message-ID: <1018629476.3cb70d64cc27e@webmail.tiscalinet.be> (raw)
In-Reply-To: <200204121614.g3CGENMn003726@hiauly1.hia.nrc.ca>
Dave,
It confirms my first idea. (I also just find back:
http://mkhppa1.esiee.fr/archive/script_toolchain).
Thanks a lot,
Joel
PS: I will send a mail to Carlos to report him this small bug and some update
Quoting John David Anglin <dave@hiauly1.hia.nrc.ca>:
> > Here am I with something confusing me about glibc building.
> >
> > In the Carlos O'Donell recipe
> > (http://www.parisc-linux.org/toolchain/PA-Linux-XC-HOWTO-04.html)
> >
> > It is set "export PATH=$PATH:$DEST/bin"
> > So at configure step it was selected gcc-3.0.4 (the last release for
> hppa-linux box)
> >
> > Naturally if I put "export PATH=$DEST/bin:$PATH", the configure of
> glibc select
> > (for me well) gcc-3.2.
> >
> > What is the right way? (for me the second)
>
> Here is the script that I use to build glibc. This installs to the
> same
> prefix that I use for gcc and binutils.
>
> #!/bin/sh
> # /bin/sh must be bash!
> export
> PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/dave/opt/
> gnu/bin
> unset LD_RUN_PATH
> unset LD_LIBRARY_PATH
> export CC=/home/dave/opt/gnu/bin/gcc
> export CFLAGS="-O2 -g"
> ../glibc/configure --build=hppa-linux --host=hppa-linux
> --target=hppa-linux --pr
> efix=/home/dave/opt/gnu --disable-profile --without-cvs --enable-add-ons
> --enabl
> e-hacker-mode &&
> make &&
> make install
>
> I tried to ensure that I am using the system tools for the build and
> install
> except for the compiler which I specify with CC. The compiler was built
> with
> --with-gnu-as and --with-gnu-ld, so it knows where to find its tools
> independent of the PATH setting.
>
> Dave
> --
> J. David Anglin dave.anglin@nrc.ca
> National Research Council of Canada (613) 990-0752 (FAX:
> 952-6605)
>
>
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next prev parent reply other threads:[~2002-04-12 16:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 17:24 [parisc-linux] "unaligned access to ... at ip=..." problem with evms and jfs joel.soete
2002-04-03 18:13 ` Randolph Chung
2002-04-04 9:46 ` joel.soete
2002-04-04 15:46 ` John David Anglin
2002-04-08 6:15 ` [parisc-linux] GCC support for dwarf2 joel.soete
2002-04-08 16:08 ` John David Anglin
2002-04-11 11:58 ` joel.soete
2002-04-11 15:31 ` John David Anglin
2002-04-11 16:35 ` joel.soete
2002-04-12 11:49 ` joel.soete
2002-04-12 16:14 ` John David Anglin
2002-04-12 16:37 ` joel.soete [this message]
2002-04-15 16:26 ` [parisc-linux] Patch to debina glibc-2.2.5 for gcc-3.2 build (was GCC support for dwarf2) joel.soete
2002-04-12 21:44 ` [parisc-linux] GCC support for dwarf2 Carlos O'Donell Jr.
2002-04-15 6:30 ` joel.soete
2002-08-03 19:27 ` [parisc-linux] "unaligned access to ... at ip=..." problem with evms and jfs Joel Soete
2002-08-07 6:11 ` Randolph Chung
2002-08-07 8:12 ` jsoe0708
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 18:19 [parisc-linux] GCC support for dwarf2 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=1018629476.3cb70d64cc27e@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=dave@hiauly1.hia.nrc.ca \
--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.