From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Errors building pkg-config: Multiple definitions
Date: Tue, 28 Mar 2017 08:47:46 +0200 [thread overview]
Message-ID: <CABDcavbteFno=65MMc-h4NZJY7MCE3L6Uy26VhKqFtJO2K7_aw@mail.gmail.com> (raw)
In-Reply-To: <CABDcavZkGoq6rafQt+QaFyh+9C_+kDd8D0KQaAMp2NpoNuXDOQ@mail.gmail.com>
Hello,
A follow up on this:
2017-03-27 19:35 GMT+02:00 Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com>:
> Hello all,
>
> Trying to rebuild the OSELAS Mini2440 BSP. Again this had been built
> previously on Ubuntu 10 and 12, now trying to rebuild on a new
> machine.
>
> ptxdist-2013.09.0
> BSP release 2013.10.0
> Host: Ubuntu 16.04.2
>
> When building the host-pkg-config package I get a ton of errors about
> multiple definitions in the internal copy of glib. Here's a short
> fragment:
>
> [...]
> ./.libs/libglib.a(gtree.o): In function `g_bit_storage':
> /home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1616:
> multiple definition of `g_bit_storage'
> testglib.o:/home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1616:
> first defined here
> ./.libs/libglib.a(gutils.o): In function `g_bit_nth_lsf':
> /home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1579:
> multiple definition of `g_bit_nth_lsf'
> testglib.o:/home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1579:
> first defined here
> ./.libs/libglib.a(gutils.o): In function `g_bit_nth_msf':
> /home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1597:
> multiple definition of `g_bit_nth_msf'
> testglib.o:/home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1597:
> first defined here
> ./.libs/libglib.a(gutils.o): In function `g_bit_storage':
> /home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1616:
> multiple definition of `g_bit_storage'
> testglib.o:/home/grodriguez/work/ptxdist/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0/platform-mini2440/build-host/pkg-config-0.25/glib-1.2.10/glib.h:1616:
> first defined here
> collect2: error: ld returned 1 exit status
The problem here is gcc 5 and the fact that "inline" has different
semantics in C99. The easiest fix here is to use gcc-4.x instead. I
can confirm that the problem is not present when building with
gcc-4.9.
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-28 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 17:35 Guillermo Rodriguez Garcia
2017-03-28 6:47 ` Guillermo Rodriguez Garcia [this message]
2017-03-28 7:52 ` Michael Olbrich
2017-03-28 8:49 ` Guillermo Rodriguez Garcia
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='CABDcavbteFno=65MMc-h4NZJY7MCE3L6Uy26VhKqFtJO2K7_aw@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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