public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103528] [12 regression] d21 doesn't build on Solaris
Date: Wed, 15 Dec 2021 22:20:23 +0000	[thread overview]
Message-ID: <bug-103528-4-nhcLqVFKuB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103528-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103528

--- Comment #5 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Rainer Orth from comment #0)
> * toplevel configure needs to make certain that the bootstrap gdc can compile
>   *and link* some trivial D program.  Letting the build proceed otherwise
> leads
>   to confusing link errors as seen here.  gnat can do away without such a
> test
>   because there are no gnat without libgnat configurations (either you have a
>   fully working GNAT or you have none), while the gdc without libphobos 
>   situation is quite common in GCC.
I'm on the side-line with that observation though, gdc without libphobos has
been defaulted in configure.tgt more because I lack the means for testing such
a broad amount of targets (such as non-x86 BSDs).  When someone does test it
(powerpc64le-freebsd) the report I get back is usually that it works fine.

Rather gdc without libphobos is more of an exception, because the compiler
heavily depends on it existing anyway, with many high-level features lowered
into calls of core druntime helper functions.  Without a runtime, this severely
limits what you can do in the language to a strict subset (that might as well
be C).

To pick a similar example, is this a bug?  Or can it be explained away with
documentation?
---
checking for long long... yes
checking size of long long... configure: error: in `/work/gcc/build/gcc':
configure: error: cannot compute sizeof (long long)
See `config.log' for more details
make[1]: *** [Makefile:4511: configure-gcc] Error 1
make[1]: Leaving directory '/work/gcc/build'
make: *** [Makefile:985: all] Error 2
---
(config.log)
configure:6450: checking size of long long
configure:6455: g++ -o conftest -g     conftest.cpp  >&5
/usr/bin/ld: cannot find -lstdc++
collect2: error: ld returned 1 exit status
configure:6455: $? = 1
configure: program exited with status 1
---

  parent reply	other threads:[~2021-12-15 22:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 12:46 [Bug d/103528] New: " ro at gcc dot gnu.org
2021-12-02 12:46 ` [Bug d/103528] " ro at gcc dot gnu.org
2021-12-02 12:49 ` ro at gcc dot gnu.org
2021-12-02 12:50 ` ro at gcc dot gnu.org
2021-12-02 13:11 ` ibuclaw at gdcproject dot org
2021-12-10  4:27 ` cvs-commit at gcc dot gnu.org
2021-12-15 22:20 ` ibuclaw at gdcproject dot org [this message]
2021-12-16 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-16 17:38 ` ibuclaw at gdcproject dot org
2021-12-16 17:41 ` ibuclaw at gdcproject dot org
2021-12-21 20:30 ` cvs-commit at gcc dot gnu.org
2022-03-09 13:52 ` rguenth at gcc dot gnu.org
2022-03-09 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-10 10:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-11  8:45 ` cvs-commit at gcc dot gnu.org
2022-03-18 11:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-04-28  8:32 ` cvs-commit at gcc dot gnu.org
2022-05-06  8:32 ` [Bug d/103528] [12/13 " jakub at gcc dot gnu.org
2023-02-21 15:02 ` rguenth at gcc dot gnu.org
2023-04-25 15:12 ` [Bug d/103528] [12/13/14 " ro 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-103528-4-nhcLqVFKuB@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).