Skip to contentSkip to conversation

CML2-2.1.3 is available

DISCUSSION Giacomo Catenazzi 2 participants 4 messages Jan 22, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 10 lines · Keith Owens
Quoted 7 lines · Giacomo Catenazzi

If autoconfigure will go in the kernel, I have not problems on filenames, but when I initially created it, I thinked ev. to distribuite it as a package. Here the name matter.

IMHO longer filename ia a good things (iff normal user should not type it).

Quoted 8 lines

autoconf autoconfigure: symlinks

        $(CONFIG_SHELL) scripts/....

make autoconf == make autoconfigure.

Watch out for the generated autoconf.h file, it might confuse some people.

Where?

I don't find it in:
http://lxr.linux.no/search?v=2.4.17&string=autoconfigure

giacomo

#2 lore raw
Quoted 8 lines · Giacomo Catenazzi
Quoted 2 lines · Keith Owens

Watch out for the generated autoconf.h file, it might confuse some people.

Where?

I don't find it in:
http://lxr.linux.no/search?v=2.4.17&string=autoconfigure

All the make *config entries generate include/linux/autoconf.h, it is the C representation of .config. Some people may think that autoconf.h is created by make autoconfig when it is really created by all *config steps.

#3 lore raw
Quoted 6 lines · Keith Owens

All the make *config entries generate include/linux/autoconf.h, it is the C representation of .config. Some people may think that autoconf.h is created by make autoconfig when it is really created by all *config steps.

I know.

My question: where do you find

autoconf autoconfigure: symlinks
$(SHELL_SCRIPT) script/...

This can cause confution, but I don't find ut in the sources.

BTW: I used 'make autoprobe' because of possible confutions, in

latter version. Now Eric will use both 'make autoconfig' and 'make autoprobe'.
The choice of name now is on Eric hands. Important is that *users* doesn't confuse it.

giacomo

#4 lore raw
Quoted 4 lines · Giacomo Catenazzi

My question: where do you find

autoconf autoconfigure: symlinks
$(SHELL_SCRIPT) script/...

You don't. That was an example of how you can have multiple targets pointing to the same code, it is not in kbuild yet.

Quoted 3 lines

BTW: I used 'make autoprobe' because of possible confutions, in latter version. Now Eric will use both 'make autoconfig' and 'make autoprobe'.

FWIW, I prefer autoprobe.