When I run "make || die" in the ebuild, this is an example # c++ -mcpu=i686 -march=i686 -O3 -pipe -fno-implicit-templates -I. -I./../include -I./../generic true -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_ST_BLKSIZE=1 -DSIZEOF_SIZE_T=4 -DSIZEOF_UNSIGNED_INT=4 -DSP_HAVE_BOOL=1 -DSP_HAVE_LOCALE=1 -DSP_HAVE_GETTEXT=1 -DSP_ANSI_CLASS_INST=1 -DSP_HAVE_SOCKET=1 -DJADE_MIF=1 -DJADE_HTML=1 -DSP_MULTI_BYTE=1 -DSGML_CATALOG_FILES_DEFAULT=\"/etc/sgml/catalog\" -DSGML_SEARCH_PATH_DEFAULT=\"/usr/share/sgml\" -DDEFAULT_SCHEME_BUILTINS=\"/usr/share/sgml/openjade-1.3/builtins.dsl\" -c -fPIC -DPIC Allocator.cxx -o Allocator.lo c++: cannot specify -o with -c or -S and multiple compilations make[2]: *** [Allocator.lo] Error 1 Note the "true" after "-I./../generic" This is from "openjade-1.3.ebuild" this is -not- appended in shell when doing a normal make, and causes the build to fail completely. workaround: comment out DEBUG in /etc/make.globals
I think that changing the name of our DEBUG variable to something more specific to gentoo will prevent conflicts like this.
OK, in CVS portage, DEBUG is now DEBUGBUILD. And you forcefully disable stripping of your ebuild by adding RESTRICT="nostrip" to your ebuild. This should close this bug. :)