public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98318] New: libcody breaks DragonFly bootstrap Date: Wed, 16 Dec 2020 12:09:06 +0000 [thread overview] Message-ID: <bug-98318-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98318 Bug ID: 98318 Summary: libcody breaks DragonFly bootstrap Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: rimvydas.jas at gmail dot com Target Milestone: --- Created attachment 49776 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49776&action=edit possible fix Since the introduction of libcody, gcc bootstrap is broken on DragonFly BSD: gmake[3]: Leaving directory '/build/trunk/libcpp' Configuring stage 1 in ./libcody configure: creating cache ./config.cache checking build system type... x86_64-unknown-dragonfly5.9 checking host system type... x86_64-unknown-dragonfly5.9 checking number of CPUs... unknown checking maintainer-mode... checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ -std=c++11 accepts -g... yes checking whether g++ -std=c++11 is for C++11... yes checking adding -Wl,--no-undefined to linker... ok /data/gg/libcody/configure: CONFIG_FILES+= ./Makesub: not found /data/gg/libcody/configure: CONFIG_FILES+= ./tests/Makesub: not found checking bugurl... github.com/urnathan/libcody checking checking... yes checking exceptions... no ... ar rc libcommon.a diagnostic.o diagnostic-color.o diagnostic-show-locus.o diagnostic-format-json.o json.o edit-context.o pretty-print.o intl.o sbitmap.o vec.o input.o version.o hash-table.o ggc-none.o memory-block.o selftest.o selftest-diagnostic.o sort.o ranlib libcommon.a gmake[3]: *** No rule to make target '../libcody/libcody.a', needed by 'cc1-checksum.c'. Stop. gmake[3]: Leaving directory '/build/trunk/gcc' gmake[2]: *** [Makefile:4781: all-stage1-gcc] Error 2 gmake[2]: Leaving directory '/build/trunk' gmake[1]: *** [Makefile:27488: stage1-bubble] Error 2 gmake[1]: Leaving directory '/build/trunk' gmake: *** [Makefile:1004: all] Error 2 The /bin/sh is almquist shell and do not take VAR+= style appends. Another issue missing <netinet/in.h> for sockaddr_in6 in netclient.cc and netserver.cc. Attached diff allows to bootstrap gcc11 once again.
next reply other threads:[~2020-12-16 12:09 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 12:09 rimvydas.jas at gmail dot com [this message] 2020-12-16 12:15 ` [Bug bootstrap/98318] " rimvydas.jas at gmail dot com 2020-12-17 7:21 ` rimvydas.jas at gmail dot com 2020-12-21 8:53 ` hliu at amperecomputing dot com 2020-12-21 14:51 ` nathan at gcc dot gnu.org 2020-12-22 2:05 ` hliu at amperecomputing dot com 2020-12-22 12:48 ` nathan at gcc dot gnu.org 2020-12-23 3:36 ` hliu at amperecomputing dot com 2020-12-23 6:51 ` hliu at amperecomputing dot com 2020-12-23 12:48 ` nathan at gcc dot gnu.org 2020-12-23 13:38 ` rimvydas.jas at gmail dot com 2020-12-23 13:43 ` rimvydas.jas at gmail dot com 2020-12-23 13:47 ` nathan at gcc dot gnu.org 2020-12-23 16:07 ` nathan at gcc dot gnu.org 2021-01-04 15:29 ` [Bug bootstrap/98318] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-28 15:04 ` jakub at gcc dot gnu.org 2021-02-25 4:27 ` rimvydas.jas at gmail dot com 2021-02-25 13:00 ` cvs-commit at gcc dot gnu.org 2021-02-25 16:59 ` nathan at gcc dot gnu.org 2021-02-26 12:21 ` rguenth 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-98318-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: linkBe 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).