Re: gcc4-core packaging bug

2013-11-02 Thread Achim Gratz
Yaakov (Cygwin/X) writes: > Actually, the RIGHT thing to do is to have Perl (updated to 5.14.4 > and) built without the CC=gcc-4 hack. Oh, absolutely. But until we have that, if anyone runs into troubles that some program which hasn't been rebuilt since the gcc update is unable to find a C compil

Re: gcc4-core packaging bug

2013-11-02 Thread Yaakov (Cygwin/X)
On 2013-11-01 15:44, Achim Gratz wrote: Andrey Repin writes: The package gcc4-core provides a compatibility symlink for programs that expect the old gcc naming scheme (like Perl). The link however is just "gcc4", while Devel::CheckLib for instance looks for "gcc4.exe". Report that to the main

Re: gcc4-core packaging bug

2013-11-01 Thread Achim Gratz
Andrey Repin writes: >> The package gcc4-core provides a compatibility symlink for programs that >> expect the old gcc naming scheme (like Perl). The link however is just >> "gcc4", while Devel::CheckLib for instance looks for "gcc4.exe". > > Report that to the maintainer of Devel::CheckLib > It S

Re: gcc4-core packaging bug

2013-11-01 Thread Andrey Repin
Greetings, Achim Gratz! > The package gcc4-core provides a compatibility symlink for programs that > expect the old gcc naming scheme (like Perl). The link however is just > "gcc4", while Devel::CheckLib for instance looks for "gcc4.exe". Report that to the maintainer of Devel::CheckLib It SHOUL

gcc4-core packaging bug

2013-11-01 Thread Achim Gratz
The package gcc4-core provides a compatibility symlink for programs that expect the old gcc naming scheme (like Perl). The link however is just "gcc4", while Devel::CheckLib for instance looks for "gcc4.exe". Regards, Achim. -- Problem reports: http://cygwin.com/problems.html FAQ: