From: "Bruce, Henry" <henry.bruce@intel.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: openjdk-7 and gcc v5
Date: Thu, 5 Nov 2015 19:21:33 +0000 [thread overview]
Message-ID: <1446751249.32751.24.camel@intel.com> (raw)
In-Reply-To: <E01AAF5B-5430-4028-948C-767910413B51@gmail.com>
On Tue, 2015-11-03 at 11:32 -0800, Khem Raj wrote:
> > On Nov 3, 2015, at 10:18 AM, Bruce, Henry <henry.bruce@intel.com>
> > wrote:
> >
> > On Thu, 2015-10-29 at 17:43 -0700, Khem Raj wrote:
> > > On Thu, Oct 29, 2015 at 4:00 PM, Bruce, Henry <
> > > henry.bruce@intel.com>
> > > wrote:
> > > > Many thanks to contributors who fixed openjdk build issues
> > > > introduced by gcc v5 and for maintainers for pushing the
> > > > updates.
> > > > However one problem remains: openjdk build fails in
> > > > openjdk/jdk/make/java/nio due to -static compiler flag being
> > > > used
> > > > in conjunction with -pthread giving error
> > > > /usr/bin/ld: cannot find -lpthread
> > > > /usr/bin/ld: cannot find -lc
> > > >
> > >
> > > its not clear how the -static flag can cause this. may be its
> > > using
> > > CC for LD or wise versa ?
> >
> > Not clear to me either, but if you create a simple file, say test.c
> >
> > int main()
> > {
> > return 0;
> > }
> >
> > and compile with gcc test.c -pthread -static
> > it fails as follows with gcc v5
> > /usr/bin/ld: cannot find -lpthread
> > /usr/bin/ld: cannot find -lc
> >
> > but compiles OK with earlier versions of gcc.
>
> isn’t this gcc on your build host ?
Yes, it is the gcc on my build host.
The openjdk recipe causes this specific makefile to build with
${CC_FOR_BUILD} which is "gcc" not ${CC}.
>
>
> >
> > >
> > > > I fixed this by removing -static flag from Makefile. Not sure
> > > > of
> > > > this was the right thing to do (so I didn't submit patch) but
> > > > it
> > > > worked for me.
> > > > I added the following to the an openjdk bbappend and it fixed
> > > > the
> > > > build and resulting jre is running OK.
> > > >
> > > > do_configure_append() {
> > > > gcc -v 2>&1 | grep 5\..
> > > > if [ "$?" == "0" ]; then
> > >
> > > why this check for gcc ?
> >
> > It only fails with gcc v5, so if it's not broken, don't fix it...
> >
> > >
> > > > sed -i s/-static//
> > > > ${B}/openjdk/jdk/make/java/nio/Makefile
> > > > fi
> > > > }
> > > >
> > > > Regards,
> > > >
> > > > Henry Bruce
> > > >
> > > > --
> > > > _______________________________________________
> > > > Openembedded-devel mailing list
> > > > Openembedded-devel@lists.openembedded.org
> > > > http://lists.openembedded.org/mailman/listinfo/openembedded-dev
> > > > el
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2015-11-05 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 23:00 openjdk-7 and gcc v5 Bruce, Henry
2015-10-30 0:43 ` Khem Raj
2015-11-03 18:18 ` Bruce, Henry
2015-11-03 19:32 ` Khem Raj
2015-11-05 19:21 ` Bruce, Henry [this message]
2015-12-15 10:06 ` Huang, Jie (Jackie)
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=1446751249.32751.24.camel@intel.com \
--to=henry.bruce@intel.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 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.