All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Does your own system matter
Date: Wed, 1 Apr 2009 23:51:59 -0700	[thread overview]
Message-ID: <200904012351.59855.raj.khem@gmail.com> (raw)
In-Reply-To: <200904012230.12120.joerg@hakker.de>

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

On Wednesday 01 April 2009 13:30:11 Jörg Bakker wrote:
> Here's another one using Ubuntu 8.10. Currently building basic bootstrap 
> images with and w/o X, distro is angstrom, branch is org.openembedded.dev, all  
> glibc. The stable branches bumped out very early (think it was the shasum 
> package), so I stayed with org.openembedded.dev.
> 
> So far, two patches were needed (gcc-cross-kernel and kernel).

using newer distributions to compile old compilers will often cause trouble because
new distributions have recent gcc versions. e.g. if you compile gcc 3.4 with gcc 4.x you will end up
in some compilation issues. It is generally preferred that you use gcc 3.4 or less to compile gcc 3.4

> I also had one 
> issue with intltool:
> 
> | checking for XML::Parser... configure: error: XML::Parser perl module is 
> required for intltool
> | FATAL: oe_runconf failed
> NOTE: Task failed: /home/jb/devel/cc/jammsession/oe/build/tmp/work/i586-
> angstrom-linux/intltool-0.40.3-r2/temp/log.do_configure.21467
> NOTE: package intltool-0.40.3-r2: task do_configure: failed
> 
> and fixed this by running:
> bitbake libxml-parser-perl-native

I think you should add DEPENDS for libxml-parser-perl in intltool recipe and retry. Depending on native package may
not be required.

> 
> Hope that gets you further down the road ...
> Joerg
> 
> Am Mittwoch 01 April 2009 18:21:57 schrieb Robert Schuster:
> > Hi,
> >
> > Mauri Sandberg schrieb:
> > > ----------------------------------------
> > >
> > >> Date: Wed, 1 Apr 2009 15:10:41 +0200
> > >> From: theBohemian@gmx.net
> > >>
> > >> I am using Ubuntu 8.10 (x86) and Debian squeeze (amd64) for OE
> > >> development. Works like a charm.
> > >
> > > That sounds reassuring. Are you building uclibc at all? Also,
> > > does it matter what versions of gcc and g++ packages you have
> > > installed locally? I am using what ever is the latests, 4.x.
> >
> > I've not build uclibc for some time. Will try again to build a current
> > image for a AVR32-based NGW when I at that machine.
> >
> > Regards
> > Robert
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

-- 
Khem Raj

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

      reply	other threads:[~2009-04-02  6:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 20:59 Does your own system matter Mauri Sandberg
2009-03-31 21:46 ` Robert Schuster
2009-04-01  9:31   ` Mauri Sandberg
2009-04-01 13:10     ` Robert Schuster
2009-04-01 13:22       ` Rafael Campos
2009-04-01 14:24         ` Mauri Sandberg
2009-04-01 14:30           ` Rafael Campos
2009-04-01 15:15           ` Detlef Vollmann
2009-04-01 13:31       ` Mauri Sandberg
2009-04-01 14:09         ` Holger Schurig
2009-04-01 16:21         ` Robert Schuster
2009-04-01 20:30           ` Jörg Bakker
2009-04-02  6:51             ` Khem Raj [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=200904012351.59855.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --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.