Skip Menu |
 

This queue is for tickets about the Alien-libtermkey CPAN distribution.

Report information
The Basics
Id: 91873
Status: open
Priority: 0/
Queue: Alien-libtermkey

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.16
Fixed in: (no value)



Subject: FreeBSD 10 does not have gcc anymore
Download (untitled) / with headers
text/plain 414b
Starting with version 10, FreeBSD does not ship anymore with gcc but with clang as the default C compiler. Therefore compilation of Alien-libtermkey fails, as src/Makefile has "gcc" hardcoded in a couple of rules. I think it's best to replace all occurrences of "gcc" with "cc". This fixes the compilation on FreeBSD 10, and I think this change shouldn't do a difference on gcc-based systems. Regards, Slaven
Download (untitled) / with headers
text/plain 769b
On Sun Jan 05 11:13:23 2014, SREZIC wrote: Show quoted text
> Starting with version 10, FreeBSD does not ship anymore with gcc but > with clang as the default C compiler. Therefore compilation of Alien- > libtermkey fails, as src/Makefile has "gcc" hardcoded in a couple of > rules. I think it's best to replace all occurrences of "gcc" with > "cc". This fixes the compilation on FreeBSD 10, and I think this > change shouldn't do a difference on gcc-based systems.
Hmm. I'm interested to hear if that actually works. Thing is this isn't necessarily invoking gcc, this is invoking libtool in its "gcc" mode. Maybe that runs gcc, maybe not. The hardcoding in the rule is more about telling libtool what to do; it's up to libtool to invoke the right program from there. -- Paul Evans
Download (untitled) / with headers
text/plain 530b
On Sun Jan 05 13:34:26 2014, PEVANS wrote: Show quoted text
> Thing is this isn't necessarily invoking gcc, this is invoking libtool > in its "gcc" mode. Maybe that runs gcc, maybe not. The hardcoding in > the rule is more about telling libtool what to do; it's up to libtool > to invoke the right program from there.
Actually on further investigation it seems that libtool isn't quite as smart as I thought it was.. :/ It does indeed just basically exec() what you tell it to. In that case, I'll adjust the 'gcc's to just 'cc's -- Paul Evans
Download (untitled) / with headers
text/plain 700b
On 2014-01-06 11:11:43, PEVANS wrote: Show quoted text
> On Sun Jan 05 13:34:26 2014, PEVANS wrote:
> > Thing is this isn't necessarily invoking gcc, this is invoking > > libtool > > in its "gcc" mode. Maybe that runs gcc, maybe not. The hardcoding in > > the rule is more about telling libtool what to do; it's up to libtool > > to invoke the right program from there.
> > Actually on further investigation it seems that libtool isn't quite as > smart as I thought it was.. :/ It does indeed just basically exec() > what you tell it to. > > In that case, I'll adjust the 'gcc's to just 'cc's
Probably the best fix is this commit: https://github.com/o11c/libtermkey/commit/11e6cf7497aa019d2e58ca04c38ef81174eb8297


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.