bug#13435: Please don't kill DJGPP support...

> I also forgot to ask a rather important question: does modern DJGPP > on Windows 2000/XP/7 etc. support file names starting with a dot? Just tested djgpp 2.04 with bash 2.05 on windows 7, and it can create files with a leading dot.

bug#13435: Please don't kill DJGPP support...

Ok, thanks!

bug#13378: Cleaning up AC_PROG_CC_C_O semantics

On 01/14/2013 11:56 AM, Stefano Lattarini wrote: > 1. It checks that *both* 'cc' and '$CC' (which might easily be 'gcc' > or 'clang') supports "-c -o" together. Why? If the user has a > broken base vendor compiler, but has installed a better one (say > GCC), why should he still b

bug#13435: Please don't kill DJGPP support...

On 01/14/2013 10:38 PM, DJ Delorie wrote: >> I also forgot to ask a rather important question: does modern DJGPP >> on Windows 2000/XP/7 etc. support file names starting with a dot? > > Just tested djgpp 2.04 with bash 2.05 on windows 7, and it can create > files with a leading dot. > Well, then i

bug#13378: Cleaning up AC_PROG_CC_C_O semantics

Hi Paul. On 01/14/2013 08:45 PM, Paul Eggert wrote: > On 01/14/13 02:24, Stefano Lattarini wrote: >> Autoconfers, WDYT? > > I think I'm lost. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378 > is a long thread. > Yeah, sorry for not giving a more clear summary. Here are the main grips I (and

bug#13378: Cleaning up AC_PROG_CC_C_O semantics

On 01/14/13 02:24, Stefano Lattarini wrote: > Autoconfers, WDYT? I think I'm lost. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378 is a long thread.

bug#13436: 3 fails in make check

Hi, I compiled automake 1.12.6 and got 3 fails when doing make check. I tried it with v1.13.1 and got the same results. echo $MACHTYPE x86_64-suse-linux I tried to use gcc + ifort and gcc + gfortran = = = = Testsuite summar

bug#13435: Please don't kill DJGPP support...

On 01/14/2013 01:23 PM, Stefano Lattarini wrote: > Severity: wishlist > > Reference: > > > I'm moving this discussion to bug-automake, so that is will be registered > in our bug tracker, for easier future reference. > > On 01/13/

bug#13435: Please don't kill DJGPP support...

Severity: wishlist Reference: I'm moving this discussion to bug-automake, so that is will be registered in our bug tracker, for easier future reference. On 01/13/2013 08:22 PM, DJ Delorie wrote: > The DJGPP project is still quite

bug#13378: Cleaning up AC_PROG_CC_C_O semantics (was: Re: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.)

[+cc bug-autoconf] Reference: On 01/13/2013 10:06 PM, Nick Bowler wrote: > On 2013-01-13, Stefano Lattarini wrote: >> On 01/13/2013 09:01 PM, Nick Bowler wrote: >>> +dnl Automatically invoke AM_PROG_CC_C_O as necessary. Since AC_PROG_CC i

bug#13378: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.

On 01/13/2013 10:06 PM, Nick Bowler wrote: > On 2013-01-13, Stefano Lattarini wrote: > >> Another useful follow-up would be to move the AM_PROG_CC_C_O in a private >> macro (to be expanded in AC_CONFIG_COMMANDS_PRE like you did above), and >> make AM_PROG_CC_C_O a no-op (without runtime deprecatio