public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Lorenzo Salvadore via Gcc <gcc@gcc.gnu.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	 Lorenzo Salvadore <developer@lorenzosalvadore.it>,
	 Jonathan Wakely <jwakely.gcc@gmail.com>,
	Andreas Tobler <andreast@freebsd.org>
Subject: Re: GCC testing on FreeBSD
Date: Sun, 28 Apr 2024 19:19:10 +0200	[thread overview]
Message-ID: <yddwmohz9pt.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <XeGxDOaMO_TqPK27Sg5Zit6W9Qr_0IijNR3o7mOcec63nGCkuJZfD7hmTXYpm54ONr17pEVwkrguKiCYMkRFJJxJFIdXvXSoqgLq5G2NH-k=@lorenzosalvadore.it> (Lorenzo Salvadore via Gcc's message of "Sun, 28 Apr 2024 13:39:17 +0000")

Hi Lorenzo,

> On Sunday, April 28th, 2024 at 12:24, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
>> On Fri, 26 Apr 2024, Jonathan Wakely wrote:
>> 
>> > How are you testing on FreeBSD?
>> > 
>> > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++
>> > testsuite it fails due to lots of these errors:
>> > 
>> > Excess errors:
>> > /usr/local/bin/ld: /tmp//ccev946q.o: relocation R_X86_64_32 against
>> > symbol `_ZTIN10__cxxabiv115__forced_unwindE@@CXXABI_1.3.2' can not be
>> > used when making a PDE object; recompile with -fPIE
>> > /usr/local/bin/ld: failed to set dynamic section sizes: bad value
>
> Hi Gerald and Jonathan!
>
> I normally test every weekly GCC snapshots through the FreeBSD ports
> framework on Cirrus, so that all my tests are publicly accessible:
> http://cirrus-ci.com/github/lsalvadore/freebsd-ports/lang/gcc11-devel
> http://cirrus-ci.com/github/lsalvadore/freebsd-ports/lang/gcc12-devel
> http://cirrus-ci.com/github/lsalvadore/freebsd-ports/lang/gcc13-devel
> http://cirrus-ci.com/github/lsalvadore/freebsd-ports/lang/gcc14-devel
>
> And of course the cirrus configuration is public as well:
> https://github.com/lsalvadore/freebsd-ports/blob/lang/gcc11-devel/.cirrus.yml

this isn't particularly helpful if you just try to build upstream GCC
for comparision with your own targets or to verify a patch of yours.
Having to go hunting for configs like this if you're not a regular
FreeBSD user is a no-no IMO.  GCC trunk should either build out of the
box or the quirks be documented in install.texi.  Otherwise, non-FreeBSD
developers will get frustrated and give up on the target, to the
detriment both of their patches and the platform.

Unfortunately, it's pretty common that targets keep necessary patches in
some ports collection of their own (usually a different one per target)
and neglect to submit them upstream.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2024-04-28 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 11:06 Jonathan Wakely
2024-04-28 10:24 ` Gerald Pfeifer
2024-04-28 10:32   ` Rainer Orth
2024-04-28 13:39   ` Lorenzo Salvadore
2024-04-28 17:19     ` Rainer Orth [this message]
2024-04-28 18:38       ` Lorenzo Salvadore
2024-04-29 12:21         ` Rainer Orth
2024-04-28 16:17   ` Jonathan Wakely

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=yddwmohz9pt.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=andreast@freebsd.org \
    --cc=developer@lorenzosalvadore.it \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jwakely.gcc@gmail.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).