From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: newlib@sourceware.org
Subject: compiling newlib
Date: Fri, 21 Aug 2020 10:20:43 +0200 [thread overview]
Message-ID: <mweeo05s10.fsf@tomate.loria.fr> (raw)
Hi,
I am new to this list. I have two questions:
1) I have a file newlib/libm/libm.a, that I have downloaded somewhere, but
I don't remember where. I'd like to know to which version of newlib it
corresponds. Is there a way to do this?
2) I downloaded newlib-3.3.0 from ftp://sourceware.org/pub/newlib/,
but I am unable to compile it on x86_64 under Linux.
Here is what I did:
$ tar xf /tmp/newlib-3.3.0.tar.gz
$ cd newlib-3.3.0
$ mkdir build
$ cd build
$ ../configure --prefix=/tmp # runs ok
$ make
The make command returns almost immediately, and there is no libm.a
file created.
I tried also the following:
$ tar xf /tmp/newlib-3.3.0.tar.gz
$ cd newlib-3.3.0
$ mkdir build
$ cd build
$ ../configure --prefix=/tmp --target=x86_64
$ make
Then make seems to do more job, however it fails with:
/bin/bash: line 2: x86_64-ar: command not found
Note: item 1 of the FAQ on https://sourceware.org/newlib/ refers to
${FULL_PATH_TO_SRC}/src/configure --prefix=`pwd` --target=XXX but there
is no src directory in the newlib-3.3.0.tar.gz tarball.
What am I doing wrong?
Best regards,
Paul Zimmermann
next reply other threads:[~2020-08-21 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 8:20 Paul Zimmermann [this message]
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
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=mweeo05s10.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--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).