| 1 |
Hi! |
| 2 |
|
| 3 |
On Tue, 21 Apr 2009, Greg KH wrote: |
| 4 |
> So, I do the following: |
| 5 |
> src_install() { |
| 6 |
> dodir /lib/firmware |
| 7 |
> cp -R "${S}/*" "${D}lib/firmware/" || die "Install failed!" |
| 8 |
> } |
| 9 |
> |
| 10 |
> but that fails badly: |
| 11 |
> >>> Install linux-firmware-20090421 into /var/tmp/portage/sys-kernel/linux-firmware-20090421/image/ category sys-kernel |
| 12 |
> cp: cannot stat `/var/tmp/portage/sys-kernel/linux-firmware-20090421/work/linux-firmware-20090421/*': No such file or directory |
| 13 |
> |
| 14 |
> Yet the files are really in that directory. |
| 15 |
> |
| 16 |
> I can't drop the trailing "*" on the cp command, otherwise we get the |
| 17 |
> directory name that the firmware was expanded into during unpack into |
| 18 |
> lib/firmware/. |
| 19 |
> |
| 20 |
> So, anyone want to apply the cluestick? |
| 21 |
|
| 22 |
I don't see an error off the top of my head. What about writing |
| 23 |
"echo" or "einfo" in front of the cp line so you see what the |
| 24 |
expanded commandline is? An ls -l{,d } "${D}lib/firmware/" in the |
| 25 |
same spot might be insightful, too. |
| 26 |
|
| 27 |
Regards, |
| 28 |
Tobias |
| 29 |
|
| 30 |
-- |
| 31 |
printk(KERN_ERR "i82092aa: Oops, you did something we didn't think of.\n"); |
| 32 |
linux-2.6.19/drivers/pcmcia/i82092.c |
Archives