From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Jeff Johnston <jjohnstn@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>, newlib@sourceware.org
Subject: Re: Various libgloss problems after recent changes
Date: Fri, 10 Feb 2023 09:54:23 -0700 [thread overview]
Message-ID: <9138400f-3819-2e46-fe64-bdab73b053d5@gmail.com> (raw)
In-Reply-To: <b808342f-4cc9-8eae-f1ad-423fdfd130f9@foss.arm.com>
On 2/10/23 04:21, Richard Earnshaw wrote:
>
>
> On 09/02/2023 22:54, Jeff Johnston wrote:
>> Hi Jeff,
>>
>> Want to try out the attached patch?
>>
>> -- Jeff J.
>>
>>
>> On Sun, Feb 5, 2023 at 7:48 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>>
>>> The fr30-elf and xstormy16-elf ports have been failing to build for
>>> about a month with this error:
>>>
>>> > fr30-elf-as -I. -I../../../../..//newlib-cygwin/libgloss/fr30/..
>>> -I./.. -idirafter
>>> ../../../../..//newlib-cygwin/libgloss/fr30/../../include -o crt0.o
>>> ../../../../..//newlib-cygwin/libgloss/fr30/crt0.s
>>>> fr30-elf-as: unrecognized option '-idirafter'
>>>
>>>
>>> For a full log:
>>>
>>> http://law-sandy.freeddns.org:8080/job/fr30-elf/1984/console
>>>
>>> Hopefully this is easy to fix so we can get those ports under regular
>>> testing again.
>>>
>>> Jeff
>>>
>>>
>
> I'm slightly confused. Why would some ports have -idirafter and some
> not, unless they're not using GCC (or a very old one).
No clue. FWIW, the tester is using the tip if the trunk for all the
components (binutils, gcc, newlib/glibc). I'm highly confident we're
not picking up old tools as the builds occur in a docker container, so
there's no pre-existing cross-tools installed. The host compiler in
those containers is roughly a year old.
jeff
next prev parent reply other threads:[~2023-02-10 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 0:48 Jeff Law
2023-02-09 22:54 ` Jeff Johnston
2023-02-10 11:21 ` Richard Earnshaw
2023-02-10 16:54 ` Jeff Law [this message]
2023-02-21 21:39 ` Jeff Johnston
2023-02-22 7:16 ` Jeff Law
2023-02-22 16:20 ` Jeff Johnston
2023-02-22 16:40 ` Jeff Law
2023-02-22 17:54 ` Jeff Law
2023-02-22 18:06 ` Jeff Johnston
2023-02-10 17:16 ` Jeff Johnston
2023-12-04 6:49 ` Mike Frysinger
2023-02-10 16:52 ` Jeff Law
2023-12-04 7:03 ` [PATCH 1/2] Revert "Fix libgloss/newlib build to conditionally use top include dir" Mike Frysinger
2023-12-04 7:03 ` [PATCH 2/2] libgloss: drop $(INCLUDES) when using $(AS) Mike Frysinger
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=9138400f-3819-2e46-fe64-bdab73b053d5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=jjohnstn@redhat.com \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).