All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Machine configs
Date: Tue, 22 Jan 2008 14:11:02 +0100	[thread overview]
Message-ID: <fn4q16$dm2$1@ger.gmane.org> (raw)

Hi,

it seems to me the machine configs for the collie need a little more
love.  At first, I thought that possibly my recent changes were faulty.
 But it seems the problems run back further.  Here is what happened,
please comment if you can shed light on the situation.

It was around January 10th that I successfull built my last image for
collie.  I had not restarted from scratch for about 4-6 weeks at least.
 A few days later, I would run into trouble with do_rootfs about
unsatisfiable dependency, even though the respective packages had just
been rebuilt a few minutes earlier.  http://oe.pastebin.com/m67158bdf is
the log from yesterday that AFAICT is identical to that problem.  It
seems that all packages in arm-oabi directory are ignored (FEED_ARCH
seems not to be set).

I then asked others to try and reproduce the situation and cleaned out
tmp to start anew.  I also reverted my monotone work dir to revision
37149b3d7b17d35e06e93ecd95c7eb36f4425da6 from Jan 7th.  I stopped
"MACHINE=collie bitbake minimal-image" when I saw

NOTE: Unpacking /export/embedded/sources/gcc-4.1.2.tar.bz2 to
/export/embedded/tmp/sonkei-0.0.1/work/armv5te-sonkei-linux/gcc-cross-4.1.2-r13/

Something is incorrect with arches for collie and this predates my
latest changes.

Can anybody please clarify why a build for collie messes with armv5te?
Why is do_rootfs ignoring arm-oabi directory?

Further tests to try and reproduce this and narrow the problem down are
also welcome.

Regards

Rolf




                 reply	other threads:[~2008-01-22 13:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='fn4q16$dm2$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.