From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: what is the proper way to build with fedora rawhide/gcc-5.0?
Date: Thu, 2 Apr 2015 09:12:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1504020908350.5421@localhost> (raw)
In-Reply-To: <8AC664C9-4035-4A3C-9AD2-A9D442C6E6EF@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2287 bytes --]
On Tue, 31 Mar 2015, Khem Raj wrote:
>
> > On Mar 31, 2015, at 12:54 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> >
> > i asked about this a few weeks ago, finally getting back to it ...
> > for better or worse, i'm running fedora rawhide, updated to the point
> > where i have gcc-5.0.0:
> >
> > $ gcc --version
> > gcc (GCC) 5.0.0 20150208 (Red Hat 5.0.0-0.10)
> > Copyright (C) 2015 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> > $
> >
> > which causes a number of build issues trying to build for something as
> > simple as qemux86.
> >
> > first, there is a linemarkers issue with gcc-5.0 that i got around
> > by adding to local.conf:
> >
> > CPPFLAGS_append= " -P”
>
> This should not be required. Can you post the failing package with error details
> it should be fixed.
>
> >
> > and there were two native build issues due to gcc-5.0 being far
> > pickier with warnings that i sidestepped with the cheap hack:
> >
> > ASSUME_PROVIDED += "elfutils-native"
> > ASSUME_PROVIDED += "binutils-native”
>
> There is 2.25 update available on my contrib tree.
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
> should help with binutils.
ok, i finally have a full build for qemux86/core-image-minimal.
things i did:
* wiped the old kernel tarball from my local source mirror -- not
sure why that fixed the kernel issue but a fresh download seems
to have done the trick.
* removed the above CPPFLAGS_append line from local.conf
* used khem's ncurses recipe
* left the two ASSUME_PROVIDED lines where they were, out of sheer
laziness since they seem to work.
enough excitement for one day ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-04-02 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 19:54 what is the proper way to build with fedora rawhide/gcc-5.0? Robert P. J. Day
2015-03-31 20:56 ` Burton, Ross
2015-03-31 21:16 ` Khem Raj
2015-03-31 21:41 ` Robert P. J. Day
2015-04-02 10:45 ` Robert P. J. Day
2015-04-02 10:56 ` Robert P. J. Day
2015-04-02 13:12 ` Robert P. J. Day [this message]
2015-04-02 16:17 ` 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=alpine.LFD.2.11.1504020908350.5421@localhost \
--to=rpjday@crashcourse.ca \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.