On 5/21/07, Andrew Fyfe <andrew@neptune-one.net> wrote:
Mateusz Jedrasik wrote:
Thursday 17 of May 2007 04:41:12 Dan McGee napisał(a):
On 5/16/07, Mateusz Jedrasik <m.jedrasik@gmail.com> wrote:
Seems the flags get exported... but my builds still dont build with the cflags specified nor with -j3...
Maybe something's wrong with the build process, i.e., the stuff gets exported but then gets neglected/overwritten during ./configure and make/gmake. Things are MUCH easier to debug if you give us a specific package or PKGBUILD that fails, instead of trying to generalize the issue. Can you do this?
-Dan
Pretty much any package doesn't work properly.
If the package uses g++ for compilation, no CFLAGS are used at all (for example, aurbuild -s nanodc) and neither are MAKEFLAGS (-j3). Well maybe they are, just the package's Makefiles cannot support it... but I doubt it.
If a package uses C (such as irssi-svn), then the flags are passed, so 'only' MAKEFLAGS don't work.
Hope this helps...
Regards,
//m.
I've tested the latest version of makepkg out of git and it works perfectly all the required variables (CFLAGS, CXXFLAGS, MAKEFLAGS, DISTCC_HOST) are exported to the shell. If a package isn't picking them up it's probably the package that's broken.
Andrew
Thanks for the testing, I (we) appreciate it. I would have to agree with Andrew now if you are having problems with the makepkg in GIT now- it would be a broken package (in the build process) rather than a broken makepkg. -Dan