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] libcody breaks DragonFly bootstrap
Date: Thu, 17 Dec 2020 07:21:21 +0000 [thread overview]
Message-ID: <bug-98318-4-y4kHTJ621E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98318-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98318
--- Comment #2 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> ---
With configure fixed in g:6d972f5183d8d476cfb008b85e224aa9b90e628d
only missing <netinet/in.h> header issue remains in netclient.cc and
netserver.cc:
g++ -std=c++11 -g -fno-enforce-eh-specs -fno-stack-protector
-fno-threadsafe-statics -fno-exceptions -fno-rtti
-fdebug-prefix-map=/data/gg/libcody/= -W -Wall -include config.h
-I/data/gg/libcody \
-MMD -MP -MF netclient.d -c -o netclient.o /data/gg/libcody/netclient.cc
/data/gg/libcody/netclient.cc: In function 'int Cody::OpenInet6(const char**,
const char*, int)':
/data/gg/libcody/netclient.cc:114:3: error: 'sockaddr_in6' was not declared in
this scope
sockaddr_in6 addr;
^~~~~~~~~~~~
/data/gg/libcody/netclient.cc:114:3: note: suggested alternative: 'sockaddr_un'
sockaddr_in6 addr;
^~~~~~~~~~~~
sockaddr_un
/data/gg/libcody/netclient.cc:115:12: error: 'addr' was not declared in this
scope
memset (&addr, 0, sizeof (addr));
next prev parent reply other threads:[~2020-12-17 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 12:09 [Bug bootstrap/98318] New: " rimvydas.jas at gmail dot com
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 [this message]
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-y4kHTJ621E@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).