Hello,

I want to configure the kernel after it was unfolded and patched within the platform/build-target/linux-3.0.31 directory, so I did change to this dir and copied the kernelconfig from the configs-direcory of ptxdist as .config:

~/svn/ptxdist/ptxdist_CPU/platform/build-target/linux-3.0.31>cp ../../../configs/kernelconfig ./.config

then I did a "make menuconfig", did *NOT* change anything but only saved the config before exiting
upon getting the question if I want to save the config.

=>as a result there is a completely different .config file. (For not bothering you with details, here is
just the linecount of the different lines in .config and the .config before:

diff .config ../../../configs/kernelconfig|wc -l
267
)

When I try to build the kernel with

"make -j2 HOSTCC=gcc ARCH=i386 CROSS_COMPILE=i686-unknown-linux-gnu- clean bzImage"

now there is a whole bunch of questions regarding some specific configurationissues, starting with
"
make -j2 HOSTCC=gcc ARCH=i386 CROSS_COMPILE=i686-unknown-linux-gnu- clean bzImage
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
*
* Restart config...
*
*
* Enable the block layer
*
Enable the block layer (BLOCK) [Y/?] y
  Support for large (2TB+) block devices and files (LBDAF) [Y/n/?] (NEW)
"


So as I found out the first modification above COULD be explained that the kernelconfig and the actual
kernelversion might differ (but I did not check whether this is the case).

But I do absolutely not understand that I still got those questions when trying to crosscompile.
BTW fyi: if I do a  native compile "make bzImage", there are no questions.

Would be nice to understand this behavior, maybe somebody does and can explain to me.

Thanks an advance for any help or hint,

Marc








--
Railtec Systems GmbH
Marc Michalewicz
Sonnenbergstrasse 19
CH-6052 Hergiswil

Tel: +41 41 632 5533
Fax: +41 41 632 5539

www.railtec-systems.ch


--
ptxdist mailing list
[email protected]

Reply via email to