Summary: | ugly hack in sgml-common for macos | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | [OLD] Unspecified | Assignee: | osx porters <osx> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | gongloo, qa |
Priority: | High | ||
Version: | 1.2 | ||
Hardware: | PPC | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
2004-09-12 15:37:26 UTC
./configure needs that statement (it looks for install-sh). Any suggestions for a better workaround? use `automake -a` then like it should have been Let's have this fixed up please. Letting it just sit in CVS isn't an option. how's this: use macos && cd ${S} && automake -a I know that's dirty too (cd ${S} is what i don't like), but i don't really see any option in the automake info pages for the equivelant. Furthermore, it leaves annoying error messages: >>> Unpacking sgml-common-0.6.3.tgz to /var/tmp/portage/sgml-common-0.6.3-r4/work macos configure.in:4: your implementation of AM_INIT_AUTOMAKE comes from an configure.in:4: old Automake version. You should recreate aclocal.m4 configure.in:4: with aclocal and run automake again. configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' Makefile.am: installing `./INSTALL' Makefile.am: installing `./COPYING' doc/man/Makefile.am:2: invalid variable `man8_DATA' >>> Source unpacked. Is this acceptable? Should I go through the whole aclocal routine? Please advise and I will commit as soon as everything looks ok. My apologies about the whole problem, and my lack of responsiveness. Fixed. Closing out bugs that've been resolved for a while now... |