From: Chris Packham <judge.packham@gmail.com>
To: Newlib <newlib@sourceware.org>
Subject: Build error for moxiebox architecture
Date: Sun, 13 Aug 2023 12:27:50 +1200 [thread overview]
Message-ID: <CAFOYHZCg1-B4fcUVji2dEe=KB1Z_ZbGt2Qkw6K0o9Lra+0QADg@mail.gmail.com> (raw)
Hi All,
I'm getting the next crosstool-ng release together and one build
failure we're having is for the moxiebox architecture:
moxie-unknown-moxiebox/lib/libc.a(libc_a-closer.o): in function `_close_r':
moxie-unknown-moxiebox/src/newlib/newlib/libc/reent/closer.c:47:
undefined reference to `_close'
and similar for _lseek, _read, _write and _sbrk
We're currently using the 4.3.0.20230120 snapshot which fails. The
older 4.2.0.20211231 succeeds (as an aside is there a convenient way
to map those snapshot versions to particular tags in the newlib-cygwin
git repo?).
Does that failure ring any bells for anyone?
next reply other threads:[~2023-08-13 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 0:27 Chris Packham [this message]
2023-08-14 10:24 ` Torbjorn SVENSSON
2023-09-19 8:04 ` Chris Packham
2023-09-20 18:24 ` Torbjorn SVENSSON
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='CAFOYHZCg1-B4fcUVji2dEe=KB1Z_ZbGt2Qkw6K0o9Lra+0QADg@mail.gmail.com' \
--to=judge.packham@gmail.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).