* Re: Building in zlib directory
@ 2002-12-27 9:16 Richard Kenner
2002-12-27 11:26 ` Jeff Sturm
2002-12-27 12:05 ` Joseph S. Myers
0 siblings, 2 replies; 5+ messages in thread
From: Richard Kenner @ 2002-12-27 9:16 UTC (permalink / raw)
To: jsturm; +Cc: gcc
GCC doesn't yet support the latest autoconf. I use 2.13.
Well, I picked up the latest one because the older one I had (2.53)
worked even worse.
Is there some web page that says what versions of these things should
be used? I can never find it when I need it.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Building in zlib directory
2002-12-27 9:16 Building in zlib directory Richard Kenner
@ 2002-12-27 11:26 ` Jeff Sturm
2002-12-27 12:05 ` Joseph S. Myers
1 sibling, 0 replies; 5+ messages in thread
From: Jeff Sturm @ 2002-12-27 11:26 UTC (permalink / raw)
To: Richard Kenner; +Cc: gcc
On Fri, 27 Dec 2002, Richard Kenner wrote:
> GCC doesn't yet support the latest autoconf. I use 2.13.
>
> Well, I picked up the latest one because the older one I had (2.53)
> worked even worse.
I don't think any 2.5x release will work correctly.
> Is there some web page that says what versions of these things should
> be used? I can never find it when I need it.
Good question. The libjava/HACKING file has some notes about automake,
but I don't know of any other guidelines.
Jeff
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Building in zlib directory
2002-12-27 9:16 Building in zlib directory Richard Kenner
2002-12-27 11:26 ` Jeff Sturm
@ 2002-12-27 12:05 ` Joseph S. Myers
1 sibling, 0 replies; 5+ messages in thread
From: Joseph S. Myers @ 2002-12-27 12:05 UTC (permalink / raw)
To: Richard Kenner; +Cc: jsturm, gcc
On Fri, 27 Dec 2002, Richard Kenner wrote:
> GCC doesn't yet support the latest autoconf. I use 2.13.
>
> Well, I picked up the latest one because the older one I had (2.53)
> worked even worse.
>
> Is there some web page that says what versions of these things should
> be used? I can never find it when I need it.
In the case of Autoconf, the FAQ:
In general, the current versions of these tools from
ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not
supported, and you will need to use Autoconf 2.13; work is in progress
to fix this problem. Also look at
ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions of
packages.
--
Joseph S. Myers
jsm28@cam.ac.uk
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Building in zlib directory
2002-12-27 8:00 Richard Kenner
@ 2002-12-27 8:28 ` Jeff Sturm
0 siblings, 0 replies; 5+ messages in thread
From: Jeff Sturm @ 2002-12-27 8:28 UTC (permalink / raw)
To: Richard Kenner; +Cc: gcc
On Fri, 27 Dec 2002, Richard Kenner wrote:
> I just picked up the latest version of automake and autoconf from ftp.gnu.org
> and when I try to build, I find that OBJEXT is null, so I get
>
> make: *** No rule to make target `adler32.'. Stop.
GCC doesn't yet support the latest autoconf. I use 2.13.
Jeff
^ permalink raw reply [flat|nested] 5+ messages in thread
* Building in zlib directory
@ 2002-12-27 8:00 Richard Kenner
2002-12-27 8:28 ` Jeff Sturm
0 siblings, 1 reply; 5+ messages in thread
From: Richard Kenner @ 2002-12-27 8:00 UTC (permalink / raw)
To: gcc
I just picked up the latest version of automake and autoconf from ftp.gnu.org
and when I try to build, I find that OBJEXT is null, so I get
make: *** No rule to make target `adler32.'. Stop.
This is on alpha Tru64.
I'm obviously doing something different from others, but I don't know what.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-12-27 18:27 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-27 9:16 Building in zlib directory Richard Kenner
2002-12-27 11:26 ` Jeff Sturm
2002-12-27 12:05 ` Joseph S. Myers
-- strict thread matches above, loose matches on Subject: below --
2002-12-27 8:00 Richard Kenner
2002-12-27 8:28 ` Jeff Sturm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).