All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] glibc broken when linked with gold Was: State of OE World, 2019-03-16
Date: Fri, 29 Mar 2019 07:37:34 -0400	[thread overview]
Message-ID: <20190329113734.GA31182@linux-uys3> (raw)
In-Reply-To: <20190328144033.GA1601@jama>

On Thu 2019-03-28 @ 03:40:33 PM, Martin Jansa wrote:
> Send for oe-core:
> https://patchwork.openembedded.org/patch/159874/
> but more information might be needed before it gets applied to oe-core
> as discussed with RP. I'll try to get serial cable working on my Nexus 5
> to test it there in runtime, but maybe someone could beat me to it with
> some more easily hackable 32bit arm board.
> 
> > > Can someone confirm that glibc built with gold works for him on arm
> > > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > > oe-core recipe?

I have an Olimex imx233-olinuxino-maxi that I build for and test regularly
(arm926ej-s, ARMv5).

Yesterday I performed two builds from master with the following configuration:

	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"
	meta-oe
	meta-python
	meta-networking      = "master:24dd9328f7ec964bbad25b7061366f9f2ff6194d"

Both builds explicitly included gobject-introspection.

The first build was done as-is (i.e. using the bfd linker). The second build
had the following in conf/local.conf:

	DISTRO_FEATURES_append = " ld-is-gold"

The default build succeeded. The gold build failed as expected while running
qemu trying to build gobject-introspection.

The good build boots on the hardware and runs fine (as far as I can tell):

	OpenEmbedded nodistro.0 imx233-olinuxino-maxi ttyAMA0

	imx233-olinuxino-maxi login: root
	root@imx233-olinuxino-maxi:~# uname -a
	Linux imx233-olinuxino-maxi 5.0.3-fslc+g20d8efe36350 #1 Thu Mar 28 17:09:20 UTC 2019 armv5tejl armv5tejl armv5tejl GNU/Linux
	root@imx233-olinuxino-maxi:~# g-ir-compiler --help
	Usage:
	  g-ir-compiler [OPTION?]

	Help Options:
	  -h, --help                    Show help options

	Application Options:
	  --includedir                  include directories in GIR search path
	  -o, --output=FILE             output file
	  -m, --module=NAME             module to compile
	  -l, --shared-library=FILE     shared library
	  --debug                       show debug messages
	  --verbose                     show verbose messages



WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: glibc broken when linked with gold Was: [oe] State of OE World, 2019-03-16
Date: Fri, 29 Mar 2019 07:37:34 -0400	[thread overview]
Message-ID: <20190329113734.GA31182@linux-uys3> (raw)
In-Reply-To: <20190328144033.GA1601@jama>

On Thu 2019-03-28 @ 03:40:33 PM, Martin Jansa wrote:
> Send for oe-core:
> https://patchwork.openembedded.org/patch/159874/
> but more information might be needed before it gets applied to oe-core
> as discussed with RP. I'll try to get serial cable working on my Nexus 5
> to test it there in runtime, but maybe someone could beat me to it with
> some more easily hackable 32bit arm board.
> 
> > > Can someone confirm that glibc built with gold works for him on arm
> > > (I haven't seen this on x86, aarch64)? Or should we just force bfd in
> > > oe-core recipe?

I have an Olimex imx233-olinuxino-maxi that I build for and test regularly
(arm926ej-s, ARMv5).

Yesterday I performed two builds from master with the following configuration:

	Build Configuration:
	BB_VERSION           = "1.40.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuseleap-15.0"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "imx233-olinuxino-maxi"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv5 thumb dsp"
	TARGET_FPU           = "soft"
	meta-freescale       = "master:08173f472244817b85fe4af8ab2add7a0090b122"
	meta-fsl-arm-extra   = "master:b4d2c8462220e7038adffc0a151767ef8da07c5d"
	meta                 = "master:aeaca9bb1b1c8bf44818945dc4b2cbd6d4b5cef2"
	meta-oe
	meta-python
	meta-networking      = "master:24dd9328f7ec964bbad25b7061366f9f2ff6194d"

Both builds explicitly included gobject-introspection.

The first build was done as-is (i.e. using the bfd linker). The second build
had the following in conf/local.conf:

	DISTRO_FEATURES_append = " ld-is-gold"

The default build succeeded. The gold build failed as expected while running
qemu trying to build gobject-introspection.

The good build boots on the hardware and runs fine (as far as I can tell):

	OpenEmbedded nodistro.0 imx233-olinuxino-maxi ttyAMA0

	imx233-olinuxino-maxi login: root
	root@imx233-olinuxino-maxi:~# uname -a
	Linux imx233-olinuxino-maxi 5.0.3-fslc+g20d8efe36350 #1 Thu Mar 28 17:09:20 UTC 2019 armv5tejl armv5tejl armv5tejl GNU/Linux
	root@imx233-olinuxino-maxi:~# g-ir-compiler --help
	Usage:
	  g-ir-compiler [OPTION?]

	Help Options:
	  -h, --help                    Show help options

	Application Options:
	  --includedir                  include directories in GIR search path
	  -o, --output=FILE             output file
	  -m, --module=NAME             module to compile
	  -l, --shared-library=FILE     shared library
	  --debug                       show debug messages
	  --verbose                     show verbose messages



  reply	other threads:[~2019-03-29 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 15:26 State of OE World, 2019-03-16 Khem Raj
2019-03-17 16:46 ` akuster808
2019-03-17 19:56   ` Khem Raj
2019-03-27 16:17 ` Martin Jansa
2019-03-27 16:35   ` Martin Jansa
2019-03-27 20:39     ` Martin Jansa
2019-03-27 22:32       ` glibc broken when linked with gold Was: " Martin Jansa
2019-03-27 22:32         ` glibc broken when linked with gold Was: [oe] " Martin Jansa
2019-03-28  5:08         ` glibc broken when linked with gold Was: " Khem Raj
2019-03-28  5:08           ` glibc broken when linked with gold Was: [oe] " Khem Raj
2019-03-28 14:40           ` glibc broken when linked with gold Was: " Martin Jansa
2019-03-28 14:40             ` glibc broken when linked with gold Was: [oe] " Martin Jansa
2019-03-29 11:37             ` Trevor Woerner [this message]
2019-03-29 11:37               ` Trevor Woerner
2019-03-29 14:14               ` [OE-core] glibc broken when linked with gold Was: " Trevor Woerner
2019-03-29 14:14                 ` glibc broken when linked with gold Was: [oe] " Trevor Woerner

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=20190329113734.GA31182@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.