configure: creating ./config.status config.status: creating Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands /usr/bin/make all-am make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] gmake: *** [all] Error 2 * * ERROR: dev-python/pyxf86config-0.3.34-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2806: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed This patch fixes it: --- configure.in.old 2008-06-01 16:24:13 +0000 +++ configure.in 2008-06-01 16:24:23 +0000 @@ -7,8 +7,6 @@ AC_PROG_CC AC_ISC_POSIX AC_PROG_LN_S -AC_PATH_PROG(MAKE,make) -AC_PROG_MAKE_SET AC_PROG_AWK AM_PROG_LIBTOOL I think I poked you a while ago about it; and you were ok with it as long as I send this upstream... well... I haven't found a bug reporting tool for it and then forgot about it. Now I'm back to it as latest hal should be fine on bsd. What is the way to report it upstream ? Or maybe just mail the author ?
Upstream is redhat bugzilla, should be a package name for it in there.
(In reply to comment #1) > Upstream is redhat bugzilla, should be a package name for it in there. > https://bugzilla.redhat.com/show_bug.cgi?id=461597
Please reopen when fixed upstream, then we can add a patch.
(In reply to comment #3) > Please reopen when fixed upstream, then we can add a patch. hmm wait, please leave it open so that I can keep track of this; this is the only remaining blocker for hal 0.5.11 on bsd, and therefore other gnome & friends stuff (reassign to bsd if you want to keep a clean bugzilla search)
(In reply to comment #4) > (In reply to comment #3) > > Please reopen when fixed upstream, then we can add a patch. > > > hmm wait, please leave it open so that I can keep track of this; this is the > only remaining blocker for hal 0.5.11 on bsd, and therefore other gnome & > friends stuff (reassign to bsd if you want to keep a clean bugzilla search) Is this trivial fix going to be ever applied? upstream doesnt seem to answer on the redhat bugzilla... probably because they don't care about bsd... This is still the only blocker for a sane hal on bsd, the ebuild already rewrites most of the broken build system therefore that pisses me off to see such pedantic conditions about upstream applying the patch holding a long standing issue.
applied & keyworded
