From: Steven Munroe <munroesj@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix s_finitel.c on ppc/ppc64
Date: Wed, 01 Feb 2006 17:33:00 -0000 [thread overview]
Message-ID: <43E0F2AE.3050702@us.ibm.com> (raw)
In-Reply-To: <20060201122123.GY4625@sunsite.mff.cuni.cz>
Jakub Jelinek wrote:
>Hi!
>
>While comparing ppc{,64} and s390{,64} abilist differences between
>older DFmode only long double capable glibc with current CVS glibc,
>I noticed we are now only exporting {__,}finitel@GLIBC_2.{1,0}
>and not also {__,}finitel@@GLIBC_2.4. Fixed thusly:
>
Thanks for finding this and the libio-ldbl.h problem. I have hit this
trying a full biarch toolchain build. But it looks there are simular
problems with sprintf and __strtold_internal. I am hitting this in the
powerpc glibc install for -msecure-plt bootstrap.
/opt/biarch/gcc41-ld/bin/powerpc-secure-gcc -o
/home/sjmunroe/toolchain/build/glibc32/malloc/memusagestat
/home/sjmunroe/toolchain/build/glibc32/malloc/memusagestat.o -lgd -lpng
-lz -lm
/opt/biarch/gcc41-ld/lib/gcc/powerpc-linux/4.1.0/../../../../lib/libm.so:
undefined reference to `finitel@GLIBC_2.4'
/opt/biarch/gcc41-ld/lib/gcc/powerpc-linux/4.1.0/../../../../lib/libm.so:
undefined reference to `sprintf@GLIBC_2.4'
/opt/biarch/gcc41-ld/lib/gcc/powerpc-linux/4.1.0/../../../../lib/libm.so:
undefined reference to `__strtold_internal@GLIBC_2.4'
collect2: ld returned 1 exit status
Will the fix be simular to finitel?
next prev parent reply other threads:[~2006-02-01 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 12:21 Jakub Jelinek
2006-02-01 17:33 ` Steven Munroe [this message]
2006-02-01 17:45 ` Jakub Jelinek
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=43E0F2AE.3050702@us.ibm.com \
--to=munroesj@us.ibm.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).