From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Christophe MONAT <christophe.monat@st.com>
Cc: newlib@sourceware.org, jjohnstn@redhat.com
Subject: Re: compiling newlib
Date: Tue, 25 Aug 2020 10:39:10 +0200 [thread overview]
Message-ID: <mwa6yj3ys1.fsf@tomate.loria.fr> (raw)
In-Reply-To: <PR3PR10MB3850AE3EE01A35C50B548F83E0570@PR3PR10MB3850.EURPRD10.PROD.OUTLOOK.COM> (message from Christophe MONAT on Tue, 25 Aug 2020 07:37:07 +0000)
Dear Christophe,
> + #include <errno.h>
> probably would have avoided the trouble to add newlib-specific code.
of course I tried, but I get with #include <errno.h>:
$ gcc e.c /localdisk/zimmerma/newlib/libm/libm.a
/usr/bin/ld: /localdisk/zimmerma/newlib/libm/libm.a(lib_a-k_standard.o): in function `__kernel_standard':
k_standard.c:(.text+0x39): undefined reference to `__errno'
/usr/bin/ld: k_standard.c:(.text+0x59): undefined reference to `__errno'
/usr/bin/ld: k_standard.c:(.text+0x7f): undefined reference to `__errno'
/usr/bin/ld: k_standard.c:(.text+0xa1): undefined reference to `__errno'
/usr/bin/ld: k_standard.c:(.text+0xc1): undefined reference to `__errno'
/usr/bin/ld: /localdisk/zimmerma/newlib/libm/libm.a(lib_a-k_standard.o):k_standard.c:(.text+0xe9): more undefined references to `__errno' follow
collect2: error: ld returned 1 exit status
Best regards,
Paul
PS: I discovered that while comparing different libraries for single-precision
functions: <https://members.loria.fr/PZimmermann/papers/accuracy.pdf>
next prev parent reply other threads:[~2020-08-25 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 8:20 Paul Zimmermann
2020-08-24 19:41 ` Jeff Johnston
2020-08-25 6:42 ` Paul Zimmermann
2020-08-25 7:37 ` Christophe MONAT
2020-08-25 8:39 ` Paul Zimmermann [this message]
2020-08-25 8:50 ` Christophe MONAT
2020-08-25 17:04 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 21:57 Xavier Pegenaute
2000-12-19 22:59 HenrySimmons17
2000-12-19 23:39 ` Alexandre Oliva
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=mwa6yj3ys1.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=christophe.monat@st.com \
--cc=jjohnstn@redhat.com \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).