Hi Karl,
I agree with most everything you wrote (and I elided now).
* Karl Berry wrote on Sat, Nov 28, 2009 at 12:06:55AM CET:
> I altered the last example to be about a mistaken upload, instead of
> retiring an existing release. In general, it seems to me that we don't
> want to suggest that it
* Юрий Пухальский wrote on Fri, Nov 27, 2009 at 11:14:04PM CET:
> It's working like a charm, the autotools system, One small thing is
> 64-bit ARFLAGS on AIX,
> but the folks out there in libtool (if i remember right) are aware of
> the problem, it seems, but i haven't investigated it yet.
Try
O
Sure. These numbers were real Automake versions though,
I know.
want to genericize the package name as well?
Yep, that's what I meant to suggest.
--symlink also allows you to pass target names other than
*-latest.tar.gz I guess, so #2 shows how --symlink-regex works while
2009/11/28 Ralf Wildenhues :
> Hello Yuri, nice to read from you again,
Hello, Ralf, nice to see you too:)
It's working like a charm, the autotools system, One small thing is
64-bit ARFLAGS on AIX,
but the folks out there in libtool (if i remember right) are aware of
the problem, it seems, but i ha
2009/11/28 Jack Kelly :
> 2009/11/28 Юрий Пухальский :
>> On Fri, Nov 27, 2009 at 4:07 PM, Jack Kelly wrote:
>>> 2009/11/27 Юрий Пухальский :
Automake links binaries through libtool too, at least in my case.
>>>
-make output---
/oracle/10.2.0.4/bin/proc CODE=ANSI_C include=.
Ralf Wildenhues wrote:
> Hmm. Can you run
> AUTOCONF="autoconf --verbose --debug" \
> automake --verbose --add-missing --foreign --copy --include-deps
> and post the output as well as (gzip'ed) the files from the leftover
> temporary directory mentioned in the output (typically /tmp/am4t...)
2009/11/28 Юрий Пухальский :
> -snip-
>>
>> My bad. I meant noinst_LIBRARIES, so you make a libcommon.a instead of
>> libcommon.la. This goes into LDADD as with libtool convenience
>> libraries.
> I haven't checked it, but does it support library dependencies like
> .la? This i use extensively.
Ye
Hi Jack,
* Jack Kelly wrote on Fri, Nov 27, 2009 at 10:37:55PM CET:
> 2009/11/28 Ralf Wildenhues:
> > That's why you should do it like this:
> >
> > .pc.$(OBJEXT):
> > ...
>
> I'm confused. Why is this better than writing a .pc.c rule? Doesn't it
> sacrifice proper dependency tracking on t
Hi Ralf,
2009/11/28 Ralf Wildenhues :
> That's why you should do it like this:
>
> .pc.$(OBJEXT):
> ...
I'm confused. Why is this better than writing a .pc.c rule? Doesn't it
sacrifice proper dependency tracking on the generated .c file?
-- Jack
Hello Yuri, nice to read from you again,
* Юрий Пухальский wrote on Fri, Nov 27, 2009 at 10:38:15AM CET:
> Automake links binaries through libtool too, at least in my case.
Yes, but it doesn't compile the objects for non-libraries using libtool,
just like Jack explained.
> And yes, it works when
2009/11/28 Юрий Пухальский :
> On Fri, Nov 27, 2009 at 4:07 PM, Jack Kelly wrote:
>> 2009/11/27 Юрий Пухальский :
>>> Automake links binaries through libtool too, at least in my case.
>>
>>> -make output---
>>> /oracle/10.2.0.4/bin/proc CODE=ANSI_C include=../../include
>>> include=/oracle
* Rich Wales wrote on Wed, Nov 25, 2009 at 07:57:49PM CET:
> I attempted to build the "gpsd" sources (gpsd.berlios.de) on an OpenBSD 4.6
> system, using autoconf 2.61 and automake 1.10. I'm getting the following:
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
On Fri, Nov 27, 2009 at 4:07 PM, Jack Kelly wrote:
> 2009/11/27 Юрий Пухальский :
>> Automake links binaries through libtool too, at least in my case.
>
>> -make output---
>> /oracle/10.2.0.4/bin/proc CODE=ANSI_C include=../../include
>> include=/oracle/10.2.0.4/lib include=/usr/include ir
Automake links binaries through libtool too, at least in my case.
-make output---
/oracle/10.2.0.4/bin/proc CODE=ANSI_C include=../../include
include=/oracle/10.2.0.4/lib include=/usr/include ireclen=4800
oreclen=4800 select_error=no release_cursor=no hold_cursor=yes
lines=yes ltype=none c
Hi Karl,
* Karl Berry wrote on Fri, Nov 27, 2009 at 04:25:37PM CET:
> First, all the existing examples in gnupload --help use automake 1.8.2b.
> This isn't either of rms' recommended version number schemes for test
> releases. Would you agree to changing to something generic, like
> foobar-0.9.90
More about gnupload --help.
First, all the existing examples in gnupload --help use automake 1.8.2b.
This isn't either of rms' recommended version number schemes for test
releases. Would you agree to changing to something generic, like
foobar-0.9.90? I'm happy to send a patch if you like, althou
2009/11/27 Юрий Пухальский :
> Automake links binaries through libtool too, at least in my case.
> -make output---
> /oracle/10.2.0.4/bin/proc CODE=ANSI_C include=../../include
> include=/oracle/10.2.0.4/lib include=/usr/include ireclen=4800
> oreclen=4800 select_error=no release_cursor=no
17 matches
Mail list logo
