public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oss at cogitri dot dev" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/95184] New: GDC reporting multiple definitions of functions where DMD and LDC do not
Date: Mon, 18 May 2020 07:51:53 +0000	[thread overview]
Message-ID: <bug-95184-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95184
           Summary: GDC reporting multiple definitions of functions where
                    DMD and LDC do not
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: oss at cogitri dot dev
  Target Milestone: ---

Created attachment 48556
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48556&action=edit
Full build log

When compiling glibd 2.1.0 with gir-to-d 0.21 with gdc 9.3.0 it errors out,
complaining about multiple definitions of functions:

/usr/lib/gcc/x86_64-alpine-linux-musl/9.3.0/../../../../x86_64-alpine-linux-musl/bin/ld:
glibd-2.0@sha/output_generated_gio_DataInputStream.d.o: in function
`_DT56_D3gio19BufferedInputStream19BufferedInputStream9__mixin1517getSeekableStructMFbZPS3gio1c5types9GSeekable':
DataInputStream.d:(.text+0x1be4): multiple definition of
`_DT56_D3gio19BufferedInputStream19BufferedInputStream9__mixin1517getSeekableStructMFbZPS3gio1c5types9GSeekable';
glibd-2.0@sha/output_generated_gio_BufferedInputStream.d.o:BufferedInputStream.d:(.text+0x10c):
first defined here

Since the source is generated via gir-to-d I don't think providing the source
makes much sense here, if you need assistance in building glibd I can help

             reply	other threads:[~2020-05-18  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  7:51 oss at cogitri dot dev [this message]
2020-05-18  8:32 ` [Bug d/95184] " ibuclaw at gdcproject dot org
2020-05-18  9:07 ` oss at cogitri dot dev
2020-05-18  9:20 ` ibuclaw at gdcproject dot org
2020-05-18 13:21 ` ibuclaw at gdcproject dot 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-95184-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).