public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: msp430-elf cross-compiler: libstdc++ supported?
Date: Tue, 8 Nov 2022 12:37:37 +0000	[thread overview]
Message-ID: <CACb0b4mYNO6KOk0cfv88GcEEtHDxA4a1aDH7a4jjdB3uRdsw1w@mail.gmail.com> (raw)
In-Reply-To: <878rklk7ws.fsf@oldenburg.str.redhat.com>

On Tue, 8 Nov 2022 at 11:22, Florian Weimer via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> I'm trying to validate a change to gcc/config/msp430/msp430.cc.
> The cross-compiler builds as far as I can tell, but I hit a snag while
> configuring libstdc++:
>
> checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[1]: *** [Makefile:12334: configure-target-libstdc++-v3] Error 1
> make[1]: Leaving directory '/root/msp/build-gcc'
>
> Is this expected?  Is libstdc++ even supported for this target?

Yes. What's your configure command? You probably need at least --with-newlib.

I think my last successful msp430 build was using:

.../gcc/configure --target=msp430-elf --prefix=$HOME/gcc/msp430-elf
--disable-libcc1 --disable-libgomp --disable-libitm --disable-libssp
--disable-libvtv --disable-nls --with-system-zlib
target_alias=msp430-elf --disable-libstdcxx-pch
--disable-full-memory-range --with-newlib --enable-libstdcxx
--enable-languages=c,c++

With the cross binutils already installed to $PREFIX/gcc/msp430-elf


  reply	other threads:[~2022-11-08 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 11:22 Florian Weimer
2022-11-08 12:37 ` Jonathan Wakely [this message]
2022-11-08 12:46   ` 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=CACb0b4mYNO6KOk0cfv88GcEEtHDxA4a1aDH7a4jjdB3uRdsw1w@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.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).