From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001694]: Missing argument in makefile
Date: Mon, 10 Dec 2007 22:20:36 -0800 [thread overview]
Message-ID: <7946fa08a0318b3cc17ceab103cb24b9@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=1694
======================================================================
Reported By: martinmeba
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1694
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 12-10-2007 20:58 PST
Last Modified: 12-10-2007 22:20 PST
======================================================================
Summary: Missing argument in makefile
Description:
Error when executing make
SVN revision for buildroot: 20636
modinfo.c: In function ?main?:
modinfo.c:338: warning: ?infosize? may be used uninitialized in this
function
/usr/bin/gcc -g -O2 -Wunused -Wall -o modinfo modinfo.o zlibsupport.o
/usr/bin/gcc -g -O2 -Wunused -Wall -o insmod.static -static insmod.o
make[1]: Leaving directory
`/home/martin/buildroot/toolchain_build_arm_nofpu/module-init-tools-3.2.2'
touch -c
/home/martin/buildroot/toolchain_build_arm_nofpu/module-init-tools-3.2.2/depmod
/usr/bin/install -D
/home/martin/buildroot/toolchain_build_arm_nofpu/module-init-tools-3.2.2/depmod
/home/martin/buildroot/build_arm/staging_dir/bin/arm-linux-depmod26
cp -dpf
/home/martin/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.config
cp: missing destination file operand after
`/home/martin/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.config'
Try `cp --help' for more information.
make: ***
[/home/martin/buildroot/project_build_arm/uclibc/linux-2.6.22.10/.configured]
Error 1
I followed the instructions to set the system up. Is there no second
argument because I didn't configure something correctly or is this a bug?
======================================================================
----------------------------------------------------------------------
hmoffatt - 12-10-07 22:20
----------------------------------------------------------------------
It's because you failed to set BR2_PACKAGE_LINUX_KCONFIG to the location of
your kernel configuration file.
Issue History
Date Modified Username Field Change
======================================================================
12-10-07 20:58 martinmeba New Issue
12-10-07 20:58 martinmeba Status new => assigned
12-10-07 20:58 martinmeba Assigned To => buildroot
12-10-07 22:20 hmoffatt Note Added: 0003074
======================================================================
next reply other threads:[~2007-12-11 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 6:20 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-13 12:26 [Buildroot] [buildroot 0001694]: Missing argument in makefile bugs at busybox.net
2007-12-11 4:58 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=7946fa08a0318b3cc17ceab103cb24b9@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