From: Denys Dmytriyenko <denis@denix.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5] qtwebkit 5.8 build issues?
Date: Mon, 12 Jun 2017 15:04:24 -0400 [thread overview]
Message-ID: <20170612190424.GW28053@denix.org> (raw)
In-Reply-To: <CAJ86T=W3YBoLXH+J16XhJ+FO_ZtW17hPX8+djgqrgVNFXkeBkg@mail.gmail.com>
On Wed, Apr 12, 2017 at 05:53:21PM -0700, Andre McCurdy wrote:
> On Wed, Apr 12, 2017 at 5:11 PM, Andreas Oberritter
> <obi@opendreambox.org> wrote:
> > On Wed, 12 Apr 2017 16:38:58 -0700
> > Andre McCurdy <armccurdy@gmail.com> wrote:
> >
> >> On Wed, Apr 12, 2017 at 3:45 PM, Andreas Oberritter
> >> <obi@opendreambox.org> wrote:
> >> > On Wed, 29 Mar 2017 19:06:14 -0400
> >> > Denys Dmytriyenko <denis@denix.org> wrote:
> >> >
> >> >> On Sun, Mar 26, 2017 at 04:30:53PM -0400, Denys Dmytriyenko wrote:
> >> >> > Hi,
> >> >> >
> >> >> > I've been having the following build issues lately with qtwebkit 5.8 from
> >> >> > master:
> >> >> >
> >> >> > | make[2]: Entering directory '/OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/build/Source'
> >> >> > | rm -f libQt5WebKit.so.5.8.0 libQt5WebKit.so libQt5WebKit.so.5 libQt5WebKit.so.5.8
> >> >> > | linking ../lib/libQt5WebKit.so.5.8.0
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `_end'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Core.so:(*IND*+0x0): multiple definition of `_end'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Gui.so:(*IND*+0x0): multiple definition of `__bss_start'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Gui.so:(*IND*+0x0): multiple definition of `_edata'
> >> >> > | /OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/recipe-sysroot/usr/lib/libQt5Gui.so:(*IND*+0x0): multiple definition of `_end'
> >> >> > | collect2: error: ld returned 1 exit status
> >> >> > | Makefile.api:92: recipe for target '../lib/libQt5WebKit.so.5.8.0' failed
> >> >> > | make[2]: *** [../lib/libQt5WebKit.so.5.8.0] Error 1
> >> >> > | make[2]: Leaving directory '/OE/master/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/build/Source'
> >> >> > | Makefile.QtWebKit:44: recipe for target 'sub-api-pri-make_first-ordered' failed
> >> >> > | make[1]: *** [sub-api-pri-make_first-ordered] Error 2
> >> >> >
> >> >> > I believe I was able to build 5.8/master before, so I'm suspecting recent
> >> >> > binutils upgrade... But I can be wrong. Would really appreciate some help
> >> >> > here. Thanks.
> >> >>
> >> >> Anyone else see this?
> >> >>
> >> >
> >> > I do. Have you been able to solve it in the meantime?
> >>
> >> Do you both have gold enabled?
> >>
> >> https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1653529
> >
> > I don't use the ld-is-gold flag, but gold gets built nevertheless. It's just not
> > the default linker. I guess qtwebkit forces its use. So the question becomes whether
> > I should set ld-is-gold or teach qtwebkit not to use gold, in order not to mix both
> > linkers.
>
> Assuming qtwebkit has a configure option to explicitly enable/disable
> gold, I'd say add a PACKAGECONFIG option.
>
> In the short term keep the PACKAGECONFIG option disabled and in the
> longer term (once qtwebkit builds successfully with gold enabled) set
> the PACKAGECONFIG option based on the testing the distro feature.
Has there been any progress on this? Is anybody looking at adding this
PACKAGECONFIG flag?
--
Denys
next prev parent reply other threads:[~2017-06-12 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 20:30 [meta-qt5] qtwebkit 5.8 build issues? Denys Dmytriyenko
2017-03-29 23:06 ` Denys Dmytriyenko
2017-04-12 22:45 ` Andreas Oberritter
2017-04-12 23:38 ` Andre McCurdy
2017-04-13 0:11 ` Andreas Oberritter
2017-04-13 0:53 ` Andre McCurdy
2017-06-12 19:04 ` Denys Dmytriyenko [this message]
2017-06-12 23:10 ` Denys Dmytriyenko
2017-06-13 12:36 ` Andreas Oberritter
2017-06-13 12:34 ` Andreas Oberritter
2017-06-13 14:36 ` Martin Jansa
2017-06-13 14:42 ` Denys Dmytriyenko
2017-06-13 16:14 ` Andre McCurdy
2017-06-14 10:19 ` Martin Jansa
2017-06-14 8:55 ` Andreas Oberritter
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=20170612190424.GW28053@denix.org \
--to=denis@denix.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-devel@lists.openembedded.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