[BUG] nasm files are not processed in automake generated Makefiles

Hello, I'm trying to build an autoconf/automake tree for the XviD project. The XviD lib uses lot of optimized asm files that must be assemble with nasm. As libtool does not support nasm natively, i had to use a tip from the the libsdl library automake files. But like libsdl (y

GNU build system support (autoconf, automake, libtool) forNetWare

Does anyone know of any past, current, or future efforts to have the GNU build system (autoconf, automake, libtool) support the NetWare platform? With some NetWare-specific configuration added to the GNU build tools, it seems feasible to run them on a Cygwin host, specifying NetWare as the targ

Re: PATCH + What might cause this failure?

Eric wrote: > Not sure whether this is relevent or not, > but it might offer a clue. [[...]] > - "automake --add-missing" didn't think install-sh was in fact >missing, because it could find the copy in pkg-root, because: [[...]] > Workaround: add this to pkg-root/distrib/configure.ac: >

Re: Support for new languages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > "Rafael" == Rafael Jesus Alcantara Perez <[EMAIL PROTECTED]> writes: > > Rafael> Is there any way of adding support for new languages to > Rafael> AUTOMAKE, without modifying the source of the main AUTOMAKE > Rafael> script (usually /usr/bin/a

Re: object `foo.$(OBJEXT)' created both with libtool and without

>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes: [...] Harlan> Suggestions on how I can remedy this problem? Yep. http://sources.redhat.com/ml/automake/2002-06/msg00199.html -- Alexandre Duret-Lutz

Re: libfoo.la is already going to be installed in `lib'

>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes: Harlan> I hope I didn't ask about this one already. Harlan> I have a Makefile.am that uses conditionals: Harlan> foo/Makefile.am: Harlan> if COND1 Harlan> libfoo = libfoo.la Harlan> endif Harlan> if COND2 Harlan> libfoo = libfoo.l

Re: header files

>>> "Neal" == Neal H Walfield <[EMAIL PROTECTED]> writes: [...] Neal> What I would like to happen is have make first run a "build-header" Neal> target in each subdirectory which causes the header files to be Neal> installed in $(top_builddir)/include (optimally via symbolic links). Neal> The

Re: files left after distclean: How to clean those?

>>> "Bob" == Bob Proulx <[EMAIL PROTECTED]> writes: Bob> DISTCLEANFILES = example.8 Bob> dist_man_MANS = example.8 dist_ means you want to distribute example.8. DISTCLEANFILES lists any files that should be cleaned to restore the tree in its 'distributed' form. So that means you don't want t

Re: files left after distclean: How to clean those?

>>> "Bob" == Bob Proulx <[EMAIL PROTECTED]> writes: [...] Bob> example.8: src/example Bob>help2man --output=example.8 ./src/example [...] Bob> But it requires help2man as a build dependency Bob> which may not exist on a developer system. Every time a user unpack your tarball and run