From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001068]: install kernel header failure.(kernel-2.6.18)
Date: Mon, 12 Feb 2007 05:44:10 -0800 [thread overview]
Message-ID: <70d79166b4e3ff84c6228dd260f1d778@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=1068
======================================================================
Reported By: jdiwu
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1068
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-09-2006 23:46 PDT
Last Modified: 02-12-2007 05:44 PST
======================================================================
Summary: install kernel header failure.(kernel-2.6.18)
Description:
configure options:
Target Architecture : i386
Target Architecture Variant : i686
Linux 2.6.18 kernel headers
output of make like:
......
toolchain/patch-kernel.sh /buildroot/tc_toolchain_build_i686/linux-2.6.18
toolchain/kernel-headers linux-2.6.18\*.patch
(cd /buildroot/tc_toolchain_build_i686/linux-2.6.18 ; \
make -j1 ARCH=i686
INSTALL_HDR_PATH=/buildroot/tc_toolchain_build_i686/linux
headers_install)
make[1]: Entering directory
`/buildroot/tc_toolchain_build_i686/linux-2.6.18'
Makefile:486:
/buildroot/tc_toolchain_build_i686/linux-2.6.18/arch/i686/Makefile: No
such file or directory
make[1]: *** No rule to make target
`/buildroot/tc_toolchain_build_i686/linux-2.6.18/arch/i686/Makefile'.
Stop.
make[1]: Leaving directory
`/buildroot/tc_toolchain_build_i686/linux-2.6.18'
make: *** [/buildroot/tc_toolchain_build_i686/linux/.configured] Error 2
======================================================================
----------------------------------------------------------------------
bernhardf - 11-22-06 14:29
----------------------------------------------------------------------
This was already fixed.
Issue History
Date Modified Username Field Change
======================================================================
10-09-06 23:46 jdiwu New Issue
10-09-06 23:46 jdiwu Status new => assigned
10-09-06 23:46 jdiwu Assigned To => uClibc
11-22-06 14:29 bernhardf Status assigned => closed
11-22-06 14:29 bernhardf Note Added: 0001781
11-22-06 14:29 bernhardf Resolution open => fixed
02-12-07 05:44 vapier Status closed => assigned
02-12-07 05:44 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70d79166b4e3ff84c6228dd260f1d778@bugs.busybox.net \
--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