public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Move closing brace outside #endif [PR104866]
Date: Fri, 11 Mar 2022 20:24:32 +0100	[thread overview]
Message-ID: <f98a59f8-e184-acef-5c96-63d94a7b111f@vollmann.ch> (raw)
In-Reply-To: <CACb0b4mWmT5upgvNjJJG2Er-AEiWbB4hgzhN09w8rkgXzh-Ecw@mail.gmail.com>

On 3/11/22 18:59, Jonathan Wakely wrote:

> Thanks. Now I'm getting a build failure because libtol wasn't created
> in the avr/libstdc++-v3 directory of the build tree, but I'll have to
> look into that next week.
> 
> /bin/sh: ../libtool: No such file or directory

Here's my configure call:

$REPO_DIR/configure \
     --prefix=$PREFIX \
     --target=avr \
     --enable-languages=c,c++ \
     --with-dwarf2 \
     --enable-multilib \
     --enable-libstdcxx \
     --disable-decimal-float \
     --disable-libffi \
     --disable-libgomp \
     --disable-libmudflap \
     --disable-libquadmath \
     --disable-libssp \
     --disable-libstdcxx-pch \
     --disable-nls \
     --without-included-gettext \
     --disable-libstdcxx-verbose \
     --disable-shared \
     --disable-threads \
     --disable-tls \
     --disable-plugin \
     --with-system-zlib \
     --with-native-system-header-dir=$PREFIX/port/include \
     --with-headers=yes \
     --with-gnu-as \
     --with-gnu-ld \
     --with-avrlibc \
     --with-build-time-tools=$PREFIX/lib/avr/bin

--disable-threads is probably wrong, as I definitly have threads
(any ISR counts as thread).  I added it in the (wrong) assumption
that it would build support for std::thread...

   Detlef

  reply	other threads:[~2022-03-11 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 21:11 Jonathan Wakely
2022-03-11 14:27 ` Detlef Vollmann
2022-03-11 15:12   ` Jonathan Wakely
2022-03-11 15:21     ` Jonathan Wakely
2022-03-11 15:35     ` Detlef Vollmann
2022-03-11 17:59       ` Jonathan Wakely
2022-03-11 19:24         ` Detlef Vollmann [this message]
2022-03-14  9:57           ` Detlef Vollmann

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=f98a59f8-e184-acef-5c96-63d94a7b111f@vollmann.ch \
    --to=dv@vollmann.ch \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --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).