texinfo-devel
[Top][All Lists]
Advanced

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

Re: 4.13.90, again


From: Stefano Lattarini
Subject: Re: 4.13.90, again
Date: Tue, 13 Nov 2012 13:43:57 +0100

On 11/13/2012 12:50 AM, Karl Berry wrote:
> I just updated http://freefriends.org/~karl/texinfo-4.13.90.tar.xz
> (maybe no typo this time :).
> 
> Stefano, if you could do your tests again, that would be great.  If it
> gets by you, I'll make it a public pretest.

-*-*-

NetBSD 5.1
==========

I see this build failure with /usr/bin/make:

../build-aux/install-sh -c -d LocaleData
../build-aux/install-sh -c -d LocaleData/de.us-ascii
../build-aux/install-sh -c -d LocaleData/de.us-ascii/LC_MESSAGES
/usr/bin/install -c -m 644  
LocaleData/de.us-ascii/LC_MESSAGES/texinfo_document.mo
usage: install [-Ubcprs] [-M log] [-D dest] [-T tags] [-B suffix]
           [-a aftercmd] [-f flags] [-m mode] [-N dbdir] [-o owner] [-g group]
           [-l linkflags] [-h hash] [-S stripflags] file1 file2
       install [-Ubcprs] [-M log] [-D dest] [-T tags] [-B suffix]
           [-a aftercmd] [-f flags] [-m mode] [-N dbdir] [-o owner] [-g group]
           [-l linkflags] [-h hash] [-S stripflags] file1 ... fileN directory
       install -d [-Up] [-M log] [-D dest] [-T tags] [-a aftercmd] [-m mode]
           [-N dbdir] [-o owner] [-g group] directory ...

(and several similar failures if I run "make -k").
That is  due to the fact that 'tp/Makefile' still uses '$<' in non-suffix
rules.  The build completes correctly if I use GNU make.

On the testsuite front (run with "ALL_TESTS=yes"):

  FAIL: parser_base_tests
  FAIL: long_tests.sh

-*-*-

Solaris 10
==========

Success in both build and testsuite if GNU make is used.  If native CCS make
is used, the build step fails, aonce again due to the use of '$<' in non-suffix
rules.

-*-*-

I don't think I'll have much time to provide further details or debugging
help for now, sorry.

Karl, Patrice, would you consider asking for access to the machines of
the GCC compiler farm yourself?  That would allow you to find and debug
such issue more easily and directly...

Best regards,
  Stefano



reply via email to

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