From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001535]: x86_64 kernel target
Date: Tue, 16 Oct 2007 14:27:15 -0700 [thread overview]
Message-ID: <d38eba3b39f7a569d71246f42018efa5@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1535
======================================================================
Reported By: kevint
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1535
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-16-2007 14:27 PDT
Last Modified: 10-16-2007 14:27 PDT
======================================================================
Summary: x86_64 kernel target
Description:
x86_64 variables not set for kernel build process in buildroot.
I have been using this trivial patch for a few months now, and it seems
like it could be useful now (considering building the kernel is now a
default option, even if you select x86_64 architecture):
diff -Naur buildroot/target/device/x86/Makefile.in
buildroot-modified/target/device/x86/Makefile.in
--- buildroot/target/device/x86/Makefile.in 2007-10-16
01:15:16.000000000 -0600
+++ buildroot-modified/target/device/x86/Makefile.in 2007-10-16
10:04:43.000000000 -0600
@@ -1,3 +1,7 @@
ifeq ($(strip $(BR2_i386)),y)
include target/device/x86/i386/Makefile.in
endif
+
+ifeq ($(strip $(BR2_x86_64)),y)
+include target/device/x86/x86_64/Makefile.in
+endif
diff -Naur buildroot/target/device/x86/x86_64/Makefile.in
buildroot-modified/target/device/x86/x86_64/Makefile.in
--- buildroot/target/device/x86/x86_64/Makefile.in 1969-12-31
17:00:00.000000000 -0700
+++ buildroot-modified/target/device/x86/x86_64/Makefile.in 2007-10-16
10:04:12.000000000 -0600
@@ -0,0 +1,19 @@
+BR2_BOARD_PATH:=target/device/x86/x86_64
+
+ifeq ($(strip $(BR2_PACKAGE_LINUX_KCONFIG)),)
+ifndef LINUX26_KCONFIG
+LINUX26_KCONFIG=$(BR2_BOARD_PATH)/linux26.config
+endif
+else
+LINUX26_KCONFIG=$(strip $(BR2_PACKAGE_LINUX_KCONFIG))
+endif
+
+ifeq ($(strip $(BR2_PACKAGE_LINUX_FORMAT)),)
+ifndef LINUX26_FORMAT
+LINUX26_FORMAT=bzImage
+endif
+else
+LINUX26_FORMAT=$(strip $(BR2_PACKAGE_LINUX_FORMAT))
+endif
+
+KERNEL_HEADERS_PATCH_DIR:=$(BR2_BOARD_PATH)/kernel-header-patches
The linux26.config and busybox.config are not included in the patch, but
they should be in the target/device/x86/x86_64 directory.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
10-16-07 14:27 kevint New Issue
10-16-07 14:27 kevint Status new => assigned
10-16-07 14:27 kevint Assigned To => buildroot
======================================================================
next reply other threads:[~2007-10-16 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 21:27 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 21:50 [Buildroot] [buildroot 0001535]: x86_64 kernel target bugs at busybox.net
2007-12-06 21:28 bugs at busybox.net
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=d38eba3b39f7a569d71246f42018efa5@bugs.uclibc.org \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox