From: Marc <dkm+newlib@kataplop.net>
To: newlib@sourceware.org
Subject: Build error for m68k using 4.4.0.20231231 and master
Date: Wed, 01 May 2024 21:14:56 +0200 [thread overview]
Message-ID: <87sez1uyxb.fsf@arrakis.kataplop.net> (raw)
Hello,
while preparing the GCC 14 builds for cross compilers on Compiler
Explorer, I'm having several issues. The easiest issue comes from new
warnings that I can silence with (not ideal, but I can get a toolchain):
-Wno-error=implicit-function-declaration -Wno-implicit-in
That "fixes" builds for msp430 and sh.
The m68k is still failing with:
[ERROR] /mnt/barryallen/dkm/git/crosstool-ng/.build/m68k-unknown-elf/src/newlib/libgloss/m68k/../read.c:24:1: error: conflicting types for 'read'; have 'int(int, void *, size_t)' {aka 'int(int, void *, long unsigned int)'}
[ERROR] make[5]: *** [Makefile:528: read.o] Error 1
[ERROR] make[5]: *** Waiting for unfinished jobs....
[ERROR] /mnt/barryallen/dkm/git/crosstool-ng/.build/m68k-unknown-elf/src/newlib/libgloss/m68k/../write.c:25:1: error: conflicting types for 'write'; have 'int(int, const void *, size_t)' {aka 'int(int, const void *, long unsigned int)'}
I've tried both 4.4.0 release and current master.
Do you already have a fix? If not, I'll probably try to fix this myself
and send a followup email with the fix.
Best regards,
Marc
reply other threads:[~2024-05-01 19:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87sez1uyxb.fsf@arrakis.kataplop.net \
--to=dkm+newlib@kataplop.net \
--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).