Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] Packages that error out during build
Date: Fri, 11 Aug 2006 06:31:10 +0200	[thread overview]
Message-ID: <00d501c6bd03$70d22690$664565d5@atmel.com> (raw)
In-Reply-To: bf61e79a0608101208v69dfe8ban49e8fd39ec28b19e@mail.gmail.com

> Hotplug:
> 
> wget --passive-ftp -q -P /home/user/buildroot/dl
> http://www.kernel.org/pub/linux/utils/kernel/hotplug//diethotplug-0.4.tar.gz
> zcat /home/user/buildroot/dl/diethotplug-0.4.tar.gz | tar -C
> /home/user/buildroot/build_i686   -xf -
> toolchain/patch-kernel.sh
> /home/user/buildroot/build_i686/diethotplug-0.4 package/hotplug/
> hotplug\*.patch
> 
> Applying hotplug.patch using plaintext:
> patching file pci.c
> patching file Makefile
> make -j1 CROSS=/home/user/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-
> DEBUG=false KLIBC=false \
>    KERNEL_INCLUDE_DIR=/home/user/buildroot/build_i686/staging_dir/include \
>    TARGET_DIR=/home/user/buildroot/build_i686/root -C
> /home/user/buildroot/build_i686/diethotplug-0.4;
> make[1]: Entering directory `/home/user/buildroot/build_i686/diethotplug-0.4'
> perl convert_usb.pl <
> /home/user/buildroot/build_i686/root/lib/modules/2.4.31/modules.usbmap
>> usb_modules.h
> /bin/sh: /home/user/buildroot/build_i686/root/lib/modules/2.4.31/modules.usbmap:
> No such file or directory
> make[1]: *** [usb_modules.h] Error 1
> make[1]: Leaving directory `/home/user/buildroot/build_i686/diethotplug-0.4'
> make: *** [/home/user/buildroot/build_i686/diethotplug-0.4/hotplug] Error 2

My guess is that "modules.usbmap" is a file that contains information 
about USB device drivers built as modules.
Hotplug will, when a USB device is inserted, load a suitable module.
"modules.usbmap" should probably be generated as a result of builing the Linux kernel
so it needs to depend on the kernel
I have no clue about the format of the file.

> 
> -- Drew
> 
> 


Please do not send mails or "reply" to ulfs at dof.se, 
since it will be routed to my GSM phone.
My email address is ulf at atmel.com

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com
Best AVR  link: www.avrfreaks.net

  parent reply	other threads:[~2006-08-11  4:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 14:39 [Buildroot] Packages that error out during build Drew Cohan
2006-08-10 17:51 ` Erik Andersen
2006-08-10 19:08   ` Drew Cohan
2006-08-10 21:03     ` Erik Andersen
2006-08-11  4:31     ` Ulf Samuelsson [this message]
2006-08-10 20:11   ` Drew Cohan
2006-08-10 21:07   ` Drew Cohan
2006-08-10 21:11     ` Erik Andersen
  -- strict thread matches above, loose matches on Subject: below --
2006-08-18 12:56 Sascha Juch
2006-08-18 13:23 ` Brian C. Lane

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='00d501c6bd03$70d22690$664565d5@atmel.com' \
    --to=ulfs@dof.se \
    --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