Em 27-09-2010 17:45, Jan Hoogenraad escreveu:
> Mauro:
>
> On my system, the call to make_kconfig reads:
> ./scripts/make_kconfig.pl /lib/modules/2.6.28-19-generic/build
> /lib/modules/2.6.28-19-generic/build 1
>
> Using $kernelsrc yields the following error:
> Global symbol "$kernelsrc" requires explicit package name at
> ./scripts/make_kconfig.pl line 694.
>
> Using
> $dmahplace="$kernsrc/include/config/ieee1394/dma.h";
> yields the following INCORRECT expansion:
> /lib/modules/2.6.28-19-generic/build/include/config/ieee1394/dma.h
> this is the place where I am building into, which is different from the place
> where Ubuntu places the include files from the package
>
> Thus I built an expression to get:
> /usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394/dma.h
> as I described in the mail of yesterday.
Huh? Are you sure that Ubuntu doesn't have a symbolic link at
/lib/modules/2.6.28-19-generic/build pointing
to /usr/src/linux-headers-2.6.28-19-generic/?
If it doesn't have, then all compat checks done by make_config_compat.pl would
fail.
> Now, I realize that the header files could ALSO be present in the build
> directory, so there should be a check on that as well, as otherwise the
> FIREDTV is incorrectly disabled on other distros, or source builds.
>
> Yes, and I know all of this is ugly ....
It is not just ugly. It will break compilation on Ubuntu with:
$ make release DIR=<some dir>
Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
