All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: building OE for an amd64 machine
Date: Thu, 29 Jan 2009 10:52:33 +0100	[thread overview]
Message-ID: <glru92$m7k$1@ger.gmane.org> (raw)
In-Reply-To: <49816E98.7080508@gmx.net>

On 29-01-09 09:53, Robert Schuster wrote:
> Hi,
> I want to build packages with OE that can run on my AMD64 system. As
> such I started a machine configuration and a CPU tune file.
>
> At first everything looks good but when glibc-initial is about to
> compiled it wants to include some header file from the kernel headers
> (asm-x64-64/socket.h) and cannot find it.
>
> The strange thing is that linux-libc-headers is not installed into any
> of the staging directories.
>
> Well, it is basically my first shot at a new machine configuration. :)
>
> I created a user branch for the amd64 support and committed those two
> patches to it:
>
> http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&h=robertschuster/amd64-target&id=20a70182e0ab8b6fad5381ea797123c6d6478dc4
> http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&h=robertschuster/amd64-target&id=6441c620a7e13d6a6f1be4fe54bf1fb7fc3e6dc5
> http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&h=robertschuster/amd64-target&id=0aeb635f90e332cfb65725147dd1f78a30b9f079
>
> I am grateful about any help to get this to work.

+PACKAGE_EXTRA_ARCH += "amd64"

That's missing an 'S' at the end

+IMAGE_FSTYPES ?= "ext2.gz"

That should the '+='

regards,

Koen




      parent reply	other threads:[~2009-01-29 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  8:53 building OE for an amd64 machine Robert Schuster
2009-01-29  9:37 ` Robert Schuster
2009-01-29  9:52 ` Koen Kooi [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='glru92$m7k$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.