All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Nicola Ranaldo <ranaldo@unina.it>
Cc: openembedded-devel@openembedded.org
Subject: Re: local.conf and DISTRO
Date: Tue, 5 Sep 2006 18:17:40 +0300	[thread overview]
Message-ID: <1123249492.20060905181740@gmail.com> (raw)
In-Reply-To: <200609051435.42809.ranaldo@unina.it>

Hello Nicola,

Tuesday, September 5, 2006, 3:35:42 PM, you wrote:

> Sorry if this is a repeated question, i googled and searched the wiki site and
> i did not found a good answer.
> I want to setup an OE environment to develop familiar/opie applications and to
> build missing packages from the installation image.
> The problem is that after a lot of manual patch (ld and libstdc++), BBMASK
> and ASSUME_PROVIDED, i finally have packages, but they depends on newer libs.
> So i have to update them on the device, mixing stable packages with unstable
> packages. When i tryied to compile the hello world application i found i
> needed a threaded qte, missing from the 0.8.4, so i mixed them too.
> I was not able to compile the last kernel, as it seems not patched for h2200.
> It's easy to make the system highly unstable.
> So i'd like to edit my local.conf to build an opie-image from sources used for
> 0.8.4 release and not from cvs.

  What CVS? Anyway, Familiar 0.8.4 was built from a separate tree (see
Familiar's home page), and you'd better use that tree if you just want
to build few packages. Otherwise, there's effort to port Fam0.8.4
changes back to OE's familiar-unstable DISTRO, see recent archives of
this list. You're welcome to help.


> May you help me?

>         Niko

-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2006-09-05 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 12:35 local.conf and DISTRO Nicola Ranaldo
2006-09-05 15:17 ` Paul Sokolovsky [this message]

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=1123249492.20060905181740@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=ranaldo@unina.it \
    /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.