public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "beagleboard at davidjohnsummers dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105681] New: libstdc++-v3 fails to build on msp430
Date: Sat, 21 May 2022 08:10:15 +0000 [thread overview]
Message-ID: <bug-105681-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105681
Bug ID: 105681
Summary: libstdc++-v3 fails to build on msp430
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: beagleboard at davidjohnsummers dot uk
Target Milestone: ---
Hi, I'm trying to build gcc for an msp430 cpu, using gcc12.1.0 binuitils-2.38
and newlib-4.2.0.20211231. Now I can build c fine, but when I try to build c++
libstdc++-v3 fails, I think becuase the msp430 is only a 16bit processor.
The specific configure command used is:
../../gcc-git/configure --with-sysroot=/home/summers/msp430
--prefix=/home/summers/msp430 --target=msp430-elf --disable-nls
--disable-werror
--with-native-system-header-dir=/home/summers/msp430/msp430-elf/include
--with-newlib --enable-languages=c,c++ --disable-nls --enable-initfini-array
--enable-target-optspace --with-gmp --with-mpfr --with-mpc --with-isl
-enable-newlib-nano-malloc
This has binutils and newlib copied into the gcc source directory. The native
system header is pointed at newlib header files.
The build fails with errors like:
In file included from
/home/summers/msp430/gcc-git/libstdc++-v3/include/precompiled/extc++.h:61:
/home/summers/msp430/src/gcc-binutils-newlib/msp430-elf/libstdc++-v3/include/ext/random:355:69:
error: narrowing conversion of '86243' from 'long int' to 'unsigned int'
[-Wnarrowing]
355 | 0x00000000U, 0xe9528d85U>
| ^
I also tried the build with the git version of gcc, last weekend (14/5/22) and
had exactly the same error.
So is this a bug, or have I configured something wrong. Does libstdc++-v3 just
need to be made 16bit aware?
next reply other threads:[~2022-05-21 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 8:10 beagleboard at davidjohnsummers dot uk [this message]
2022-05-21 18:10 ` [Bug libstdc++/105681] " redi at gcc dot gnu.org
2022-05-22 9:01 ` beagleboard at davidjohnsummers dot uk
2022-05-22 16:05 ` mikpelinux at gmail dot com
2022-05-23 6:51 ` rguenth at gcc dot gnu.org
2022-05-26 20:04 ` beagleboard at davidjohnsummers dot uk
2022-05-26 20:24 ` redi at gcc dot gnu.org
2022-05-26 20:57 ` redi at gcc dot gnu.org
2022-05-26 20:59 ` redi at gcc dot gnu.org
2022-05-26 21:10 ` redi at gcc dot gnu.org
2022-05-26 21:31 ` cvs-commit at gcc dot gnu.org
2022-05-26 21:33 ` [Bug libstdc++/105681] [12 Regression] " redi at gcc dot gnu.org
2022-05-27 7:22 ` beagleboard at davidjohnsummers dot uk
2022-05-27 8:27 ` redi at gcc dot gnu.org
2022-06-08 15:52 ` cvs-commit at gcc dot gnu.org
2022-06-08 16:10 ` redi at gcc dot gnu.org
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=bug-105681-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).