From: Joel Soete <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>,
parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] back to glibc-2.3.3 & gcc-3.4.1 pb
Date: Thu, 02 Sep 2004 19:34:32 +0000 [thread overview]
Message-ID: <413775C8.3060108@tiscali.be> (raw)
Hello Carlos,
I co yesterday glibc cvs (ie 2004 09 01) and apply your patch 2004-08-24.
I install debian gcc-3.4.1-7 and the build of this the libc with this compiler failed :(
seems in _dl_make_fptr() I need much more work, ...
I so retry to build with gcc-3.3 (3.3.4-7 deb) and the build just finished with success, so I launch the check now (yes more then
7h on a c110 ;).
That said, it's the first time that I compare configure log and notice some differences, excepted :
@@ -26,8 +26,8 @@
checking for ld... ld
checking version of ld... 2.15, ok
checking for pwd... /bin/pwd
-checking for hppa-linux-gcc... (cached) /usr/bin/gcc-3.4
-checking version of /usr/bin/gcc-3.4... 3.4.1, ok
+checking for hppa-linux-gcc... (cached) hppa-linux-gcc
+checking version of hppa-linux-gcc... 3.3.4, ok
checking for gnumake... no
checking for gmake... no
checking for make... make
To help to read - as related to 3.4 and + with 3.3 (and yes unstable so binutils 2.15)
@@ -78,7 +78,7 @@
checking for -z combreloc... no
checking for -z execstack... yes
checking for -fpie... no
-checking for -fno-unit-at-a-time... yes
+checking for -fno-unit-at-a-time... no
checking whether cc puts quotes around section names... no
checking for assembler .weak directive... yes
checking for assembler line separator... !
@@ -89,7 +89,7 @@
checking for DWARF2 unwind info support... no_registry_needed
checking for __builtin_expect... yes
checking for __builtin_memset... no
-checking for redirection of built-in functions... yes
+checking for redirection of built-in functions... no
checking for local label subtraction... yes
checking for __thread... no
checking for libgd... no
Is it usefull to try to force gcc-3.4 to work without -fno-unit-at-a-time and (even though I don't know yet how) without
'redirection of built-in functions' (even thought according to patch description:
<http://gcc.gnu.org/ml/gcc-patches/2003-04/msg02045.html> this last one is supposed to help glibc build?)
TIA for advise,
Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next reply other threads:[~2004-09-02 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:34 Joel Soete [this message]
[not found] ` <20040903154019.GR32474@baldric.uwo.ca>
[not found] ` <4138B043.2020009@tiscali.be>
[not found] ` <20040904162953.GE32474@baldric.uwo.ca>
[not found] ` <413AE748.3030207@tiscali.be>
[not found] ` <413AFB1F.7010407@tiscali.be>
2004-09-06 20:03 ` [parisc-linux] Re: back to glibc-2.3.3 & gcc-3.4.1 pb Carlos O'Donell
2004-09-06 20:26 ` Joel Soete
2004-09-06 22:02 ` Carlos O'Donell
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=413775C8.3060108@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@baldric.uwo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox