All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: madwifi
Date: Tue, 05 Dec 2006 16:02:25 +0100	[thread overview]
Message-ID: <45758A01.1030203@linuxdevelopment.de> (raw)
In-Reply-To: <d46153c40612050629v8bdfcd2i32fa9858f916605f@mail.gmail.com>

Dear Andrew

Is there a specific reason why you work with the .oz354 tree ?
This tree is old and i think not maintained anymore ,, ( people correct
me if am wrong )

Also that you miss tmp/work/ARCHITECURE directory tells me that you
should consider a
mtn update in order to sync your tree to the current state .. then
please use .dev tree .

btw : how is your compulab ?  we also evaluate it here and i am getting
good results also using the current .dev tree

rob_w
> Ok, I tried a few more things this morning, but I'm still getting
> errors.  Here's what I'm working with:
>
> OE Build Configuration:
> BB_VERSION     = "1.6.3"
> OE_REVISION    = "dbe2d7e445c33fd9403d6edaf6ec36d1857ada98"
> TARGET_ARCH    = "arm"
> TARGET_OS      = "linux"
> MACHINE        = "compulab-pxa270"
> DISTRO         = "generic"
> DISTRO_VERSION = ".dev-snapshot-20061205"
> TARGET_FPU     = "soft"
> I am using the .oz354x branch of OE.
>
> I first tried adding the following to my machine.conf file:
> BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
> DEPENDS += "madwifi-ng"
>
> Which promptly broke my build with a circular dependency:
> ERROR: /stuff/org.openembedded.dev/packages/quilt/quilt-native_0.45.bb
> depends on itself (eventually)
> ERROR: upwards chain is: gpe-image (gpe-image) -> ipkg-native
> (ipkg-native) -> pkgconfig-native (pkgconfig-native) ->
> autoconf-native (autoconf-native) -> quilt-native (quilt-native) ->
> madwifi-ng (madwifi-ng) -> ipkg-utils-native (ipkg-utils-native)
>
> I then tried adding the following to my gpe-image.bb file:
> GPE_EXTRA_INSTALL += "madwifi-ng"
> DEPENDS += "madwifi-ng"
>
> I also tried a few combinations of adding madwifi-ng to
> GPE_EXTRA_INSTALL, DEPENDS, and RDEPENDS to gpe-image.bb to see if
> dumb luck would help ... it didn't.
>
> Other than the circular dependency error, I always get:
> ERROR: Nothing provides runtime dependency madwifi-ng
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>   




  reply	other threads:[~2006-12-05 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 22:02 madwifi Andrew Paulsen
2006-12-05  9:50 ` madwifi Justin Patrin
2006-12-05 14:29   ` madwifi Andrew Paulsen
2006-12-05 15:02     ` Robert Wörle [this message]
2006-12-05 15:38       ` madwifi Marcin Juszkiewicz
2006-12-05 15:41       ` madwifi Andrew Paulsen
  -- strict thread matches above, loose matches on Subject: below --
2005-02-10 18:15 madwifi Ronald G. Minnich

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=45758A01.1030203@linuxdevelopment.de \
    --to=robert@linuxdevelopment.de \
    --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.