From: Denys Dmytriyenko <denys@ti.com>
To: Matt Schuckmann <Matt.Schuckmann@planar.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: i686 binutils failing to build for SDK 7.0 build
Date: Tue, 5 Aug 2014 14:33:15 -0400 [thread overview]
Message-ID: <20140805183313.GD23523@edge> (raw)
In-Reply-To: <4B07ADD556F70043925DA2E9C5D4346D2FD85EA024@MSXBEBVT12.planar.net>
On Tue, Aug 05, 2014 at 11:19:35AM -0700, Matt Schuckmann wrote:
> > -----Original Message-----
> > From: Denys Dmytriyenko [mailto:denys@ti.com]
> > Sent: Tuesday, August 05, 2014 11:07 AM
> > To: Matt Schuckmann
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] i686 binutils failing to build for SDK 7.0
> > build
> >
> > On Tue, Aug 05, 2014 at 10:44:28AM -0700, Matt Schuckmann wrote:
> > > I'm trying to build a basic image using Arago, SDK 7.0 config
> > > (configs/amsdk/amsdk-07.00.00.00-config.txt) and binutils 2.20.1 is
> > > failing to compile for the i686 host system.
> > > I'm building on a Ubuntu 14.04 32bit VM.
> > >
> > > My bitbake command is:
> > > MACHINE=am335x-evm;bitbake core-image-minimal
> > >
> > > The errors are:
> > > binutils-native/2.20.1-r9/binutils-2.20.1/bfd/doc/bfd.texinfo:326:
> > unknown command `colophon'
> > > binutils-native/2.20.1-r9/binutils-2.20.1/bfd/doc/bfd.texinfo:337:
> > unknown command `cygnus'
> > >
> > > It looks like this was a known problem for building binutils that has
> > > been fixed a long time ago and since SDK 7.0 is released code I would
> > > have assumed the problem was taken care for the Arago build so I'm a
> > > little puzzled why I'm getting this now.
> >
> > Matt,
> >
> > Since you are using amsdk-07.00.00.00-config.txt config, you are
> > building the same exact version that was released as AMSDK 7.0. That
> > config is not being updated to pick up any latest code.
> >
> > If you want to try latest code base, you better off trying arago-daisy-
> > config.txt That would pull in everything latest from corresponding
> > Daisy branches, which is the latest stable release.
>
> Denys,
>
> I intentionally picked SDK 7.0 because is it "tested" and released code so I
> figured it would have a better chance of working and being supported. If
> that is not the case please let me know. I want a good stable point to start
> development of my own image for a custom am335x board.
>
> I did just figure out that the problem is the newer version of texinfo
> (version 5.2) packaged with Ubuntu 14.04 is not compatible with the older
> version of binutils (version 2.20.1) that is built for SDK 7.0. I manually
> downgraded my system to texinfo 4.13a and got past the error.
Matt,
That is fine - if you want to base your work on an official release, you
should stick to AMSDK 7.0 config. I thought you were trying to get the latest
code pulled in, which would be a different approach.
AMSDK 7.0 was based on Dylan, which is now 3 versions behind the latest Yocto
Project release. It was validated on Ubuntu 12.04 (and 10.04), so it may have
incompatibility issues with newer Linux distros, like you found out. This is a
more generic issue - the wider the time gap between the versions of the tools
being used (e.g. Linux host distro, cross toolchain, etc) and the components
being built (e.g. kernel, bootloader, user space apps, etc), the higher
chances are for extra issues, breakage and other weird problems...
--
Denys
next prev parent reply other threads:[~2014-08-05 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:44 i686 binutils failing to build for SDK 7.0 build Matt Schuckmann
2014-08-05 18:07 ` Denys Dmytriyenko
2014-08-05 18:19 ` Matt Schuckmann
2014-08-05 18:33 ` Denys Dmytriyenko [this message]
2014-08-05 18:24 ` Cooper Jr., Franklin
2014-08-05 18:45 ` Denys Dmytriyenko
2014-08-05 18:55 ` Matt Schuckmann
2014-08-05 19:16 ` Cooper Jr., Franklin
2014-08-05 19:24 ` Denys Dmytriyenko
2014-08-05 19:06 ` Cooper Jr., Franklin
2014-08-05 19:50 ` Denys Dmytriyenko
2014-08-22 6:40 ` Arnaud Janvier
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=20140805183313.GD23523@edge \
--to=denys@ti.com \
--cc=Matt.Schuckmann@planar.com \
--cc=meta-arago@arago-project.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.