Re: How may I modify and rebuild a OE package?

modify the file and do a oemake --cmd=compile <pkgname> (or cmd=make).
Sometime it works to edit the file and do a oemake <whatever>-image
again.

regards,

Koen
Op 12-sep-04 om 23:22 heeft Vadim Abrossimov het volgende geschreven:

> Hello,
>
> May someone advise me what would be the easiest way to modify a file in
> a OE package and then to rebuild it?
> When I modify a file in the work directory
> (e.g.
> build-arm/tmp/work/busybox-1.00-rc3-r2/busybox-1.00-rc3/modutils/
> modprobe.c) and then do "oemake busybox" it doesn't recompile the
> modified file.
> If I just go to the
> build-arm/tmp/work/busybox-1.00-rc3-r2/busybox-1.00-rc3 and do "make"
> it
> compiles for i386 :-<
>
> BTW, I may explain why I wanted to change modprobe.
>
> Probably you have seen this error message trying to load a module:
>
> "Using /lib/modules/2.6.8.1-hh0/kernel/drivers/base/soc-device.ko
> insmod: cannot insert
> `/lib/modules/2.6.8.1-hh0/kernel/drivers/base/soc-device.ko': File
> exists (-1): File exists"
>
> I assume that the reason is that there is no difference between '-' and
> '_' symbols in module's names. It happens that kernel returns always
> '_'
> in /proc/modules.
> When busbox's modprobe process a request it first check if the module
> has been already loaded comparing the file name ('soc-devices' in our
> case) with the names of the loaded modules from /proc/modules (where
> 'soc-devices' is registered under 'soc_devices').
> That's why it always tries to load soc-devices and fails up from the
> second try.
>
> So I wanted to check my assumption ....
>
> regards,
> Vadim
>
>
>
>
>
>
> _______________________________________________
> H2200-port mailing list
> H2200-port@handhelds.org
> https://handhelds.org/mailman/listinfo/h2200-port
>
Received on Sun Sep 12 17:43:22 2004