[uClibc] buildroot improvement questions

[Thomas Cameron]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nathanael Noblet wrote:
|
| On Mar 24, 2005, at 12:37 PM, David Bachelart wrote:
|
|> On Thu, Mar 24, 2005 at 11:06:09AM -0800, Nathanael Noblet wrote:
|>
|>> Just a few questions on how your patch works. I'm just wondering if the
|>> behavior I'm seeing is the intended behavior. I applied your patch.
|>> Then copied my .config to configs/myconfig_defconfig, then running make
|>> myconfig_defconfig, it basically copies my config to the .config which
|>> is then used in the following make to make the target. Is that what is
|>> supposed to happen?
|>
|>
|> Yes, it is.
|
|
| Any opposition, or reason to why it isn't something like make -f
| myconfig to specify the config? I realize that the -f flag is one that
| is sent to make, but some type of switch that would look for a config
| file in the configs/ directory and fail out if not there? or like
| make CONF=myconfig [packagename] ?
|
|
| ------------------------------------------------------------------------
|
| _______________________________________________
| uClibc mailing list
| uClibc at uclibc.org
| http://uclibc.org/mailman/listinfo/uclibc

The `make CONF=myconfig` option is the best, as it would prevent any
potential for a config name being mistaken as an actual make target. For
instance, if I have a section in a .mk file labeled
"i686-something-silly" and I have a config file named
"i686-something-silly", I will no doubt run into an issue with the wrong
thing happening. Probably (hopefully) unlikely, but better to prevent an
issue than fix an issue. (see: Buffer Overflows)

- --
Tom Cameron
tom<at>drdabbles.us
http://drdabbles.us
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCQziqO6EIpi17KSQRAs4GAJwPEX+S0ETuNS2pNWE7noMqnGNOOwCfYXN8
vd6LNr7hfoYVEK6UI/egyGk=
=7/4v
-----END PGP SIGNATURE-----