From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building x86_64 target
Date: Mon, 11 Jan 2010 16:11:04 -0500 [thread overview]
Message-ID: <4B4B93E8.7090202@cbnco.com> (raw)
In-Reply-To: <4B4B9189.3080906@rambler.ru>
Hi,
I think there are a few people building for x86_64 using out-of-tree
configurations. Here's my machine config for an HP Proliant server, for
what it's worth. It contains a few ugly hacks. I've seen smarter, less
ugly ways of doing it, submitted as patches - but I don't think they got
applied up till now.
The config below was written before the staging changes a few months
back, so there are some references to e.g. layout_libdir that may need
to be changed to libdir.
##########################################
PREFERRED_VERSION_linux = "2.6.31"
TARGET_ARCH = "x86_64"
# We can't reuse the same -native builds as 32-bit machines, because
# ours need to be staged into staging/blah/lib64 instead of lib.
# Set blah to x86_64-buildoe64-linux to keep them separate.
BUILD_VENDOR = "-buildoe64"
layout_base_libdir = "${layout_base_prefix}/lib64"
layout_libdir = "${layout_exec_prefix}/lib64"
# Some packages install files into /lib/packagename, not /lib64/packagename.
FILES_${PN} += "${prefix}/lib/${PN}/*"
FILES_${PN}-dbg += "${prefix}/lib/${PN}/.debug"
# glibc's sysdeps/unix/sysv/linux/configure script only fixes
# libc_cv_slibdir if prefix is "/usr". With prefix of "", we need to fix it
# so libc libs don't get installed into /lib.
export libc_cv_slibdir="/lib64"
# Serial console settings for sysvinit
SERIAL_CONSOLE = "57600 ttyS0"
USE_VT = "0"
MACHINE_FEATURES = "kernel26 pci ext2 x86"
PREFERRED_PROVIDER_virtual/kernel = "linux"
KERNEL_IMAGETYPE = "bzImage"
MACHINE_EXTRA_RRECOMMENDS = " kernel-modules"
udevdir = "/dev"
OLDEST_KERNEL = "2.6.17"
GLIBC_ADDONS = "nptl"
GLIBC_EXTRA_OECONF = "--with-tls"
# Make task-boot include bootloader
MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "syslinux-extlinux syslinux-mbr"
##########################################
Mike
Perepelica Alexander wrote:
> Hello!
>
> Why OE don't provide default configs for x86_64 target (on market exists
> many industrial PC with core 2 duo and other 64-bit CPU) is this some
> forbidden themes or nobody build target for thouse CPU?
>
> Thank you!
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-01-11 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 21:00 Building x86_64 target Perepelica Alexander
2010-01-11 21:11 ` Michael Smith [this message]
2010-01-11 21:24 ` Perepelica Alexander
2010-01-11 21:48 ` Michael Smith
2010-01-11 21:52 ` Perepelica Alexander
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=4B4B93E8.7090202@cbnco.com \
--to=msmith@cbnco.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.