Re: gcc4-core packaging bug
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 compiler, add the .exe suffix to the compatibility link. I've only mentioned it here because I recently got a new machine at work and wondered why I couldn't build some Perl modules anymore until I remembered that I had re-linked the compilers on the old one. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gcc4-core packaging bug
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 maintainer of Devel::CheckLib It SHOULD NOT check for .exe suffix under cygwin. Yes it should, since it does not need to know about the .exe magic Cygwin performs. Besides, it gets that information from %Config, which in turn comes from Cygwin's own Perl. Once the compatibility link is named gcc-4.exe, the .exe magic ensures that both checking for an executable named gcc-4 and gcc-4.exe will succeed, so that's the right thing to do and not patching whatever number of Perl modules and/or other build scripts. Actually, the RIGHT thing to do is to have Perl (updated to 5.14.4 and) built without the CC=gcc-4 hack. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gcc4-core packaging bug
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 SHOULD NOT check for .exe suffix under cygwin. -- WBR, Andrey Repin (anrdae...@yandex.ru) 02.11.2013, 00:33 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gcc4-core packaging bug
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 SHOULD NOT check for .exe suffix under cygwin. Yes it should, since it does not need to know about the .exe magic Cygwin performs. Besides, it gets that information from %Config, which in turn comes from Cygwin's own Perl. Once the compatibility link is named gcc-4.exe, the .exe magic ensures that both checking for an executable named gcc-4 and gcc-4.exe will succeed, so that's the right thing to do and not patching whatever number of Perl modules and/or other build scripts. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
