Hi, I don't know whether this is common knowledge or intended behaviour
but:
The AbiWord build system which uses 'Makefile' for a custom (non-automake)
build and 'GNUmakefile[.{in|am}]' for building with automake+autoconf
automake-1.5 is incompatible with this because it assumes (in depout.m4)
t
Hi, I notice automake still assumes that makefiles are called "Makefile"
(see depout.m4, lines 27-28) and not "GNUmakefile".
I posted a patch a while back but got ignored. Please could someone add
the two lines which are necessary.
Regards, Frank
Francis James Franklin
[EMAIL PROTECTED]
It's g
On 30 Dec 2001, Tom Tromey wrote:
> F.J.> Hi, I notice automake still assumes that makefiles are called
> F.J.> "Makefile" (see depout.m4, lines 27-28) and not "GNUmakefile".
> I ran into this problem in a different context, and I checked in a
> more general fix for it.
v. cool, thanks.
Happy Ne
Please do something about this deluge of spam! It's driving me nuts!
Sorely aggravated,
Frank
Francis James Franklin
[EMAIL PROTECTED]
It's getting them wrong that is living, getting them wrong and wrong and
wrong and then, on careful reconsideration, getting them wrong again.
That's how we kno
> We've stopped most of the shit from Korea based on simple filtering
Thank you for that, at least.
> BTW, it's driving me nuts too, but I'm out of filtering ideas...
Allow only messages containing the line "Dear Automake,"? Maybe not.
Regards, Frank
Francis James Franklin
[EMAIL PROTECTED]
> There is no point in debating about spam here, it becomes spam by
> itself.
Especially if you receive every e-mail twice...
Frank
Francis James Franklin
[EMAIL PROTECTED]
It's getting them wrong that is living, getting them wrong and wrong and
wrong and then, on careful reconsideration, gett
On Fri, 1 Feb 2002, [iso-8859-7] ÁëÝîáíäñïò Êáñõðßäçò (Alexandros Karypidis) wrote:
> I am trying to understand how convenience libriaries work. Using the dir
> structure "project/src/libX", where X is 1 & 2, I want to create 2
> convenience libraries in project/src/lib1 & project/src/lib2, th
I'm not distinguishing between dynamic & static. Libraries are libraries.
An example from CVS libwmf:
libwmf_la_LIBADD = libwmflite.la ipa/libipa.la $(LIBGD) $(LIBTRIO)
where libwmflite.la is not convenience but the other three are. Generally
all are built as static & shared libraries, but that'
I'd like to add in support for Objective-C (*.m) and Objective-C++ (*.mm).
I know about the work-around using the suffix rule, but it doesn't handle
dependencies...
Without having looked in any detail at automake, I'm guessing I may have
to add support into libtool (possibly even autoconf) as wel
> The problem we have is ucd-snmp choked on autoconf 2.52 and forced us
> to roll back to 2.13. With autoconf 2.13 we cannot upgrade the
> automake to 1.6 which requires autoconf 2.52. Can you see the problem
> now?
I often have fun with this kind of incompatibility. I'm no expert, but
I've fou
On Tue, 12 Mar 2002, Major A wrote:
> I would like to use automake with autoconf to build a project written
> in Objective C. What is the easiest way of doing that?
>
> All I have done so far is to create a standard configure.in (with a
> test for libobjc) and a standard Makefile.am with "test_SO
> > > we just upgrading to
> >
> > > automake 1.6(from 1.4)
> > > autoconf 2.53 (from 2.13)
> > > libtool 1.4.2 (from 1.3.5)
Excuse me for asking the obvious, but have you configured & installed all
three under the same prefix (e.g., ./configure --prefix=/usr)?
Frank
Fra
12 matches
Mail list logo
