bug#8880: depcomp for Portland Group Compilers: get rid of file locking hack?

Reading the documentation provided here: I see that the the '-MD' option should also accept an argument: -MD,filename (pgcpp only) Generate make dependence lists and print them to file filename. maybe we could we use this

bug#8880: [PATCH] add pgcc support to depcomp

Reference: Hi Dave, Jeff. On 02/25/2012 03:22 AM, Dave Goodell wrote: > Portland Group C Compiler support based on a code from Jeff Daily @ PNNL > via the automake list and automake bug #8880: > > [SNIP] > The paperwork issues have been finally

bug#8880: [FYI] {depcomp-pgcc} depcomp: style changes to Portland Group Compilers support

* lib/depcomp (pgcc): Quote 'like this', not `like this'. Other minor quoting improvements. Remove a commented-out command. In comments, use proper capitalization and punctuation. Make a more consistent use of whitespace. Make fatal error messages more nicely formatted, and send them to standa

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 12:42 PM, Stefano Lattarini wrote: > > In the light of our discussion, attached is the patch I'd finally like > to push. WDYT? Looks fine to me (although I have not actually tested it). -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization library http://li

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 2012-07-12 16:37, Stefano Lattarini wrote: > On 07/12/2012 04:00 PM, Peter Rosin wrote: >> >> Stefano Lattarini wrote: >>> >>> Since that requirement is only needed for bootstrapping, I could send >>> you a (patched) tarball to test (so that you'll only require an >>> autoconf >= 2.62). Would t

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 07:06 PM, Eric Blake wrote: > On 07/12/2012 10:23 AM, Stefano Lattarini wrote: > >>> Other than that, the only supported method in existing POSIX for >>> checking for equal files is by parsing 'ls -i' output; but I don't know >>> if 'ls -i' is portable to ancient hosts. >>> >> I was

bug#11893: Regression in automake 1.12.1 on Mac OS X

On 2012-07-12 17:48, Eric Blake wrote: > On 07/12/2012 08:37 AM, Stefano Lattarini wrote: > Agreed (albeit it does its dirty work for now). Any suggestion on how to make it more reliable? >>> >>> Is test /usr/bin/CC -ef /usr/bin/cc portable enough? >>> >> I have no idea ... it seems to

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 11:06 AM, Eric Blake wrote: Minor correction: > > That said, /bin/RMDIR is probably completely portable, but seems like it ^ not > would be reliable in practice. -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization librar

bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 10:23 AM, Stefano Lattarini wrote: >> Other than that, the only supported method in existing POSIX for >> checking for equal files is by parsing 'ls -i' output; but I don't know >> if 'ls -i' is portable to ancient hosts. >> > I was fearing this would have got quickly complex and mes

bug#11924: t/aclocal7.sh fails after updating from 1.12.1 to 1.12.2

forcemerge 11924 11896 close 11924 thanks On 07/12/2012 10:15 AM, Peter Simons wrote: > Hi, > Hi Peter, thanks for the report. > we have recently updated from Automake 1.12.1 to 1.12.2 in the NixOS Linux > distribution. That change caused a unit test failure in t/aclocal7.sh. The > complete buil

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

Hi Eric. On 07/12/2012 05:48 PM, Eric Blake wrote: > On 07/12/2012 08:37 AM, Stefano Lattarini wrote: > Agreed (albeit it does its dirty work for now). Any suggestion on how to make it more reliable? >>> >>> Is test /usr/bin/CC -ef /usr/bin/cc portable enough? >>> >> I have no idea ...

bug#11924: t/aclocal7.sh fails after updating from 1.12.1 to 1.12.2

Hi, we have recently updated from Automake 1.12.1 to 1.12.2 in the NixOS Linux distribution. That change caused a unit test failure in t/aclocal7.sh. The complete build log is available here: http://hydra.nixos.org/build/2786726 Unfortunately, the log shows very little information about the na

bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 08:37 AM, Stefano Lattarini wrote: >>> Agreed (albeit it does its dirty work for now). Any suggestion on >>> how to make it more reliable? >> >> Is test /usr/bin/CC -ef /usr/bin/cc portable enough? >> > I have no idea ... it seems to work on Cygwin 1.5 though. In general, 'test a

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 07/12/2012 04:00 PM, Peter Rosin wrote: > > Stefano Lattarini wrote: >> >> Since that requirement is only needed for bootstrapping, I could send >> you a (patched) tarball to test (so that you'll only require an >> autoconf >= 2.62). Would that be more acceptable? > > Shoot! > Sent in private

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

On 2012-07-12 10:51, Stefano Lattarini wrote: > Hi Peter. > > On 07/11/2012 11:21 PM, Peter Rosin wrote: >> On 2012-07-11 14:44, Stefano Lattarini wrote: >>> On 07/09/2012 07:04 PM, Max Horn wrote: >>> I am currently looking into packaging automake 1.12.1 for Fink

bug#10766: bug#11893: Regression in automake 1.12.1 on Mac OS X

Hi Peter. On 07/11/2012 11:21 PM, Peter Rosin wrote: > On 2012-07-11 14:44, Stefano Lattarini wrote: >> On 07/09/2012 07:04 PM, Max Horn wrote: >> >>> I am currently looking into packaging automake 1.12.1 for >>> Fink on Mac OS X 10.7. >>> Doing that, several test sui