From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Andreas Tobler <andreast@freebsd.org>,
Lorenzo Salvadore <developer@lorenzosalvadore.it>,
gcc@gcc.gnu.org
Subject: Re: GCC testing on FreeBSD
Date: Sun, 28 Apr 2024 12:32:58 +0200 [thread overview]
Message-ID: <ydd1q6p22w5.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <866dda5e-c983-ac16-de71-05b685536cd7@pfeifer.com> (Gerald Pfeifer's message of "Sun, 28 Apr 2024 12:24:09 +0200 (CEST)")
Hi Gerald,
> 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
>
> my first reaction was to recommend using binutils instead of /usr/bin/ld
> which is LLD 16.0.6 or similar (since a while ago FreeBSD switched to that
> toolchain as part of the base system).
right: some time ago I tried bootstrapping trunk on FreeBSD 14.0 myself,
which was a very rough journey unfortunately. I've filed a number of
PRs for the issues found. They should all be referenced in
PR target/112959 install.tex needs updates on FreeBSD
which is primarily a call for documention so the next unwary non-FreeBSD
developer won't run into all the same known issues again.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2024-04-28 10:33 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 [this message]
2024-04-28 13:39 ` Lorenzo Salvadore
2024-04-28 17:19 ` Rainer Orth
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=ydd1q6p22w5.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).