fredrik.holmqvist@xxxxxxxxx wrote: > Author: tqh > Date: 2011-10-30 00:00:33 +0200 (Sun, 30 Oct 2011) > New Revision: 42985 > Changeset: https://dev.haiku-os.org/changeset/42985 > > Modified: > haiku/trunk/src/bin/coreutils/lib/Jamfile > haiku/trunk/src/bin/network/wget/Jamfile > Log: > Now that we can have custom buildflags allow Haiku to build with -Os which > needs some functions not only as defines. > > Modified: haiku/trunk/src/bin/coreutils/lib/Jamfile > =================================================================== > --- haiku/trunk/src/bin/coreutils/lib/Jamfile 2011-10-29 21:51:43 UTC (rev > 42984) > +++ haiku/trunk/src/bin/coreutils/lib/Jamfile 2011-10-29 22:00:33 UTC (rev > 42985) > @@ -24,6 +24,7 @@ > basename.c > basename-lgpl.c > buffer-lcm.c > + c-ctype.c > c-strcasecmp.c > c-strtod.c > c-strtold.c > > Modified: haiku/trunk/src/bin/network/wget/Jamfile > =================================================================== > --- haiku/trunk/src/bin/network/wget/Jamfile 2011-10-29 21:51:43 UTC (rev > 42984) > +++ haiku/trunk/src/bin/network/wget/Jamfile 2011-10-29 22:00:33 UTC (rev > 42985) > @@ -34,6 +34,7 @@ > > BinCommand wget : > build_info.c > + c-ctype.c > cmpt.c > connect.c > convert.c Assuming that you're referring to your previous BuildSetup change, I'm fully confused now. How does allowing to specify custom compilation flags relate to adding a new source file regardless of those compilation flags? CU, Ingo