From: Matthias Klose <doko@ubuntu.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Andrew Stubbs <ams@codesourcery.com>,
Tobias Burnus <tobias@codesourcery.com>,
gcc-help@gcc.gnu.org
Subject: Re: GCC 10, nvptx target: newlib build failure?
Date: Fri, 17 Jul 2020 14:04:40 +0200 [thread overview]
Message-ID: <e35c4c75-24cc-4de1-dfde-c91aec498981@ubuntu.com> (raw)
In-Reply-To: <yxfpmu527s6d.fsf@hertz.schwinge.homeip.net>
Hi,
sorry for not following-up earlier. This was an issue on my side, trying to
build newlib with fortify source by mistake ...
Sorry, Matthias
On 6/16/20 8:59 PM, Thomas Schwinge wrote:
> Hi Matthias!
>
> Andrew relayed the following to me:
>
> <doko> ams_cs, Tobias__: can you build the nvptx offload compiler on the branch? I get:
> <doko> In file included from /<<PKGBUILDDIR>>/src-nvptx/newlib/libc/include/ssp/stdio.h:34,
> <doko> from /<<PKGBUILDDIR>>/src-nvptx/newlib/libc/include/stdio.h:800,
> <doko> from ../../../../../../src-nvptx/newlib/libc/stdio/gets.c:62:
> <doko> ../../../../../../src-nvptx/newlib/libc/stdio/gets.c:96:1: error: expected declaration specifiers or '...' before '__builtin_object
> <doko> _size'
> <doko> 96 | gets (char *buf)
> <doko> | ^~~~
> <doko> make[10]: *** [Makefile:1096: lib_a-gets.o] Error 1
> <doko> this is newlib 3.3.0, unchanged from the previous build
> <doko> gcc-10 branch
>
> Earlier today, I built releases/gcc-10 branch at commit
> 7d249d84e4c1be7c6f857c3a9d7791623a0e9d00, with newlib at commit
> 6d79e0a58866548f435527798fbd4a6849d05bc7 (tag: newlib-3.3.0),
> successfully.
>
> Tobias also stated that he "did a build of GCC 10 (the branch) and it did
> *not* fail".
>
> Hmm.
>
> Do you have any local patches applied that might be relevant?
>
>
> Grüße
> Thomas
> -----------------
> Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
> Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
>
prev parent reply other threads:[~2020-07-17 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:59 Thomas Schwinge
2020-07-17 12:04 ` Matthias Klose [this message]
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=e35c4c75-24cc-4de1-dfde-c91aec498981@ubuntu.com \
--to=doko@ubuntu.com \
--cc=ams@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=thomas@codesourcery.com \
--cc=tobias@codesourcery.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).