[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build problem: gzip help message is displayed

From: Keith Thompson
Subject: Re: Build problem: gzip help message is displayed
Date: Mon, 22 May 2006 01:07:53 -0700
User-agent: Mutt/1.4.1i

On Mon, May 22, 2006 at 12:24:48AM -0700, Paul Eggert wrote:
> Keith Thompson <address@hidden> writes:
> > When I build bison-2.2 from source (on Solaris 9), the gzip help
> > message shows up several times in the output log.
> Thanks for the bug report, but we need to look into this in a little
> more detail before patching Bison, as I don't observe this behavior
> when I build Bison 2.2 from source on Solaris 9 (sparc).  I include
> the output at the end of this message.
> > The problem seems to be in the file "Makefile.maint":
> That file is meant only for maintainers; it shouldn't be used if
> all you're doing is building and installing.  Maintainers are
> expected to have recent-enough editions of the build tools, and
> gzip 1.2.4 is not recent enough.
> But I'm puzzled that you'd be running 1.2.4 on Solaris 9.  On Solaris
> 9, /usr/bin/gzip --version outputs "gzip 1.3.3-patch.1".  Perhaps you
> have an older version of gzip that you built yourself?  If so, please
> try getting rid of it.

I also saw your later message, so some of this may be redundant.

I don't know what "Makefile.maint" is for, but it is being invoked.
All I'm doing is "./configure --prefix=...; make; make install".

Yes, /usr/bin/gzip is gzip 1.3.3-patch.1, and yes, I have my own build
of gzip 1.2.4 (it's actually 1.2.4a).  I'm a bit confused about that.
1.2.4a is the most recent version of gzip on ftp.gnu.org, and it's
over 7 years old.  alpha.gnu.org has 1.3.4 and 1.3.5.  Do you know
why the "official" release is so old?  (Probably I should take this
up with the gzip maintainers.)

Keith Thompson (The_Other_Keith) address@hidden  <http://www.ghoti.net/~kst>
San Diego Supercomputer Center           <*>  <http://users.sdsc.edu/~kst>
We must do something.  This is something.  Therefore, we must do this.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]