Paul Eggert wrote:
> "Support" is a relative term. If you find a new bug in SunOS 4.1.4,
> Sun will not fix it for you, even if you have purchased a standard
> software maintenance contract from Sun. I don't call that "support",
> even if Sun does.
>
> By my definition, Sun doesn't "support" Su
Hi,
I tried the "make check" of 1.7.2 on Tru64Unix using AFS filesystem and
have found the following failed:
XFAIL: auxdir2.test
XFAIL: cond17.test
FAIL: obsolete.test - automake bug, see below
FAIL: yacc7.test - bison bug, actually compiler optimization bug
Unfortunately, I cannot find out w
"Dr. David Kirkby" <[EMAIL PROTECTED]> writes:
> although you are saying it is still an operating system supported by
> Sun
"Support" is a relative term. If you find a new bug in SunOS 4.1.4,
Sun will not fix it for you, even if you have purchased a standard
software maintenance contract from Su
I have a program that uses lex and yacc and I'm trying to make it work
completely with automake. The problem I'm having is that the lex source
includes a header generated by yacc but the automake generated makefile
doesn't capture that dependency. The result is that the build tries to
run lex an
Paul Eggert wrote:
>
> "Dr. David Kirkby" <[EMAIL PROTECTED]> writes:
>
> > SunOs 4.1.4
>
> Sun has been withdrawing support for that OS. Since September 2000
> Sun has not issued patches for new bugs in that operating system. On
> September 30, Sun will further transition SunOS 4.1.4 to "cust
Hello automake team,
I'm using
AM_INIT_AUTOMAKE([foreign 1.5 no-define dist-bzip2])
which will create a tar.gz and tar.bz2 dist. How can I prevend automake
from
building the tar.gz dist, since there isn't a target like no-gzip-dist.
Thanks
Olaf
