public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: Iain Sandoe <idsandoe@googlemail.com>,
	libffi-discuss@sourceware.org,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PING] libffi: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951]
Date: Thu, 26 Oct 2023 07:32:47 -0600	[thread overview]
Message-ID: <5bf12011-0f62-4c31-bb3a-ae121493cb79@gmail.com> (raw)
In-Reply-To: <87y1frw1db.fsf@euler.schwinge.homeip.net>



On 10/25/23 02:30, Thomas Schwinge wrote:
> Hi!
> 
> Ping.
> 
> 
> Grüße
>   Thomas
> 
> 
> On 2023-09-12T12:58:27+0200, I wrote:
>> Hi!
>>
>> On 2020-04-20T14:18:40+0100, "Maciej W. Rozycki via Gcc-patches" <gcc-patches@gcc.gnu.org> wrote:
>>> Fix a problem with the libffi testsuite using a method to determine the
>>> compiler to use resulting in the tool being different from one the
>>> library has been built with, and causing a catastrophic failure from the
>>> inability to actually choose any compiler at all in a cross-compilation
>>> configuration.
>>
>> This has since, as far as I can tell, been resolved properly by H.J. Lu's
>> GCC commit 5be7b66998127286fada45e4f23bd8a2056d553e,
>> "libffi: Integrate build with GCC", and
>> GCC commit 4824ed41ba7cd63e60fd9f8769a58b79935a90d1
>> "libffi: Integrate testsuite with GCC testsuite".
>>
>>> Address this problem by providing a DejaGNU configuration file defining
>>> the compiler to use, via the CC_FOR_TARGET TCL variable, set from $CC by
>>> autoconf, which will have all the required options set for the target
>>> compiler to build executables in the environment configured
>>
>> As we've found, this is conceptually problematic, as discussed in
>> <https://inbox.sourceware.org/875y868a4b.fsf@euler.schwinge.homeip.net>
>> "Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951]".
>> I therefore suggest to apply to GCC libffi the conceptually same changes
>> as I've just pushed for libgomp:
>> <https://inbox.sourceware.org/874jjzzqc2.fsf@euler.schwinge.homeip.net>
>> "libgomp: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR91884, PR109951]".
>> OK to push the attached
>> "libffi: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951]"?
OK (patch didn't appear inline, but hopefully you've got enough context 
to know it's the libffi bits getting ACK'd).

jeff

      reply	other threads:[~2023-10-26 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 13:18 [PATCH v5 GCC] libffi/test: Fix compilation for build sysroot Maciej W. Rozycki
2020-04-22 18:04 ` Jeff Law
2020-04-25 20:33   ` Maciej W. Rozycki
2020-04-29 17:14     ` Jeff Law
2020-04-29 20:48       ` Florian Weimer
2023-09-12 10:58 ` libffi: Consider '--with-build-sysroot=[...]' for target libraries' build-tree testing (instead of build-time 'CC' etc.) [PR109951] (was: [PATCH v5 GCC] libffi/test: Fix compilation for build sysroot) Thomas Schwinge
2023-10-25  8:30   ` [PING] " Thomas Schwinge
2023-10-26 13:32     ` Jeff Law [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=5bf12011-0f62-4c31-bb3a-ae121493cb79@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=thomas@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).