Hello,
forgive my ignorance on the subject: what are the (desired) semantics of
elisp files?
Currently, you trip over Automake bugs when you use lisp files in
subdirs (with or without subdir-objects):
lisp_LISP = sub/am.el
or use nobase_:
nobase_lisp_LISP = sub/am.el
Elias reported part of
On 10/06/2009 09:52 PM, Ralf Wildenhues wrote:
[ adding automake@ ]
Hello Ralf,
* Ralf Corsepius wrote on Tue, Oct 06, 2009 at 05:49:52PM CEST:
a) AM_SILENT_RULES are harmful (I know, you know that I think about
this (mal-) "feature" this way - Working around the issues they are
causing in Fed
On 10/12/2009 08:26 PM, William Tracy (wtracy) wrote:
Hello,
I'm trying to cross-compile a library that uses GNU Autotools (Google
Coredumper, to be specific) for PPC using the MontaVista tool chain. The
sequence of commands I'm following is:
$ ./configure --host=ppc CC=/path/to/gcc CXX=/pa
This is a semi-embedded Linux system that I am trying to build for.
MontaVista is a Linux distribution that also provides a cross-compiling
toolchain--their own builds of the GNU toolchain, really. Their build
follows their own interesting naming convention, which isn't making this
simpler. >_<
T
Hi William,
On 10/12/2009 12:26 PM, William Tracy (wtracy) wrote:
I'm trying to cross-compile a library that uses GNU Autotools (Google
Coredumper, to be specific) for PPC using the MontaVista tool chain. The
sequence of commands I'm following is:
$ ./configure --host=ppc CC=/path/to/gcc CXX=/p
Hello,
I'm trying to cross-compile a library that uses GNU Autotools (Google
Coredumper, to be specific) for PPC using the MontaVista tool chain. The
sequence of commands I'm following is:
$ ./configure --host=ppc CC=/path/to/gcc CXX=/path/to/g++
$ make
$ [next step would normally be "m
