Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@openembedded.org
Subject: New IXP4XX-based Machine
Date: Wed, 31 Jan 2007 17:15:35 -0500 (EST)	[thread overview]
Message-ID: <1170281735.26425@gatekeeper.stellarwerx.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

Hello!

As I have stated before, I am a bit new, so please bear with me.

I am trying to bring up OE on a new IXP4XX-based machine and having a little trouble with the "proper" way to do it.  For example, I created a whole new machine config, inserting what I think should be machine-specific settings, and importing the (now somewhat-defunct) ixp4xx.conf configuration (and later the ixp4xxbe.conf configuration).  My bootstrap-image gets everything compiled, but when it goes to build the rootfs, ipkg fails looking for task-base.

My question is not so much about getting ipkg to work (I have found several ways), but more about the "proper" way so that I don't go "spinning into the grass" in the future.  I noticed that during the rootfs build that the "ixp4xxbe" "arch" was not in the ipkg config file, so all of my "*_ixp4xxbe.ipk" files were completely ignored - stuff like "task-base"!  I ultimately had to append "armv5te" and "ixp4xxbe" to PACKAGE_EXTRA_ARCHS and that worked, but I worked on this on-and-off for over a week to figure it out.  I really don't want to do that again when/if I try to bring up another machine.

My question is - should I even be attempting to define a new machine and including ixp4xxbe.conf in it?  Should I define my own machine by copying the contents of ixp4xxbe.conf?  Should I have specified the "ixp4xxbe" machine file in my local.conf along with the extra (what I think should be) machine config?  Or should I define my own distro and put that machine config there?  What is the most appropriate way to do this?

Thank you!
-Mark Gollahon

             reply	other threads:[~2007-01-31 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 22:15 Mark Gollahon [this message]
2007-02-01 20:58 ` New IXP4XX-based Machine Rod Whitby
2007-02-01 22:48   ` Mark Gollahon
2007-02-01 23:49     ` Rod Whitby
2007-02-02  2:40       ` Mark Gollahon

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=1170281735.26425@gatekeeper.stellarwerx.com \
    --to=golly@stellarwerx.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox