From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [meta-oe][PATCH] mariadb: -native also needs gold workaround
Date: Mon, 4 Jan 2016 19:24:58 +0100 [thread overview]
Message-ID: <20160104182458.GB5744@jama> (raw)
In-Reply-To: <CAMKF1soMFt_EGLUF8T61+7BcaureScErMsDyRdc-ZxLk3x1eFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
On Mon, Jan 04, 2016 at 10:15:23AM -0800, Khem Raj wrote:
> On Mon, Jan 4, 2016 at 9:52 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Wed, Dec 30, 2015 at 02:57:55PM +0100, Koen Kooi wrote:
> >> When the host distro uses gold mariadb-native fails to build.
> >>
> >> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> >> ---
> >> meta-oe/recipes-support/mysql/mariadb.inc | 3 +++
> >> 1 file changed, 3 insertions(+)
> >>
> >> diff --git a/meta-oe/recipes-support/mysql/mariadb.inc b/meta-oe/recipes-support/mysql/mariadb.inc
> >> index a6826c3..6a55476 100644
> >> --- a/meta-oe/recipes-support/mysql/mariadb.inc
> >> +++ b/meta-oe/recipes-support/mysql/mariadb.inc
> >> @@ -60,6 +60,9 @@ PACKAGECONFIG[setupdb] = ", ,,${PN}-setupdb"
> >> # https://mariadb.atlassian.net/browse/MDEV-5982
> >> TARGET_CFLAGS += "-fuse-ld=bfd"
> >>
> >> +BUILD_CFLAGS += "-fuse-ld=bfd"
> >> +BUILD_CXXFLAGS += "-fuse-ld=bfd"
> >
> > Unfortunately this breaks builds on older hosts with older gcc
> >
> > | cc1: error: unrecognized command line option '-fuse-ld=bfd'
> > http://errors.yoctoproject.org/Errors/Details/25859/
> >
> > Should we consider Ubuntu-12.04 insanely old?
> >
>
> Its still maintained and supported until 2017 I believe.
By Canonical yes:
http://www.ubuntu.com/info/release-end-of-life
but that doesn't automatically make it good distribution for OE builds, I'm playing
devils advocate here, because most jenkins slaves I have access to are
currently using 12.04 (that's why I've noticed this issue in first place).
I was already considering upgrading them to 14.04 and people can use
build-appliance-image if they cannot just upgrade their host distro.
FWIW: Poky already dropped it from SANITY_TESTED_DISTROS in Fido release:
commit b528712a076ad2fd08ec8a3cbcd7aefd612d999f
Author: Lucian Musat <george.l.musat@intel.com>
Date: Mon Mar 23 12:35:12 2015 +0200
meta-yocto/distro: Updated SANITY_TESTED_DISTROS.
Added OpenSUSE-13.2, Fedora 21. Removed poky 1.6 and Ubuntu 12.04.
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-01-04 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 13:57 [meta-oe][PATCH] mariadb: -native also needs gold workaround Koen Kooi
2015-12-30 18:34 ` Khem Raj
2015-12-30 19:06 ` Koen Kooi
2015-12-31 8:14 ` Koen Kooi
2015-12-31 8:39 ` Khem Raj
2016-01-04 17:52 ` Martin Jansa
2016-01-04 18:15 ` Khem Raj
2016-01-04 18:24 ` Martin Jansa [this message]
2016-01-04 18:30 ` Khem Raj
2016-01-18 9:47 ` Robert Yang
2016-01-18 11:57 ` Martin Jansa
2016-01-18 19:03 ` Khem Raj
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=20160104182458.GB5744@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--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