Bug #84354 for Encode-Detect: Encode::Detect 1.01 assumes gcc

Mon Apr 01 17:33:41 2013 pfudd [...] binkmail.com - Ticket created

Subject:	Encode::Detect 1.01 assumes gcc
Date:	Mon, 1 Apr 2013 14:33:17 -0700
To:	bug-Encode-Detect [...] rt.cpan.org
From:	"P Fudd" <pfudd [...] binkmail.com>

Hello! I'm compiling Encode::Detect on Solaris10 with the Sun Studio 12 C Compiler, and there are problems. 1. In Build.PL, there's this: extra_compiler_flags => ['-x', 'c++', '-Iinclude'], The '-x c++' argument is not understood by this compiler. This was fixed by a wrapper around the system-provided cc in /opt/SUNWspro/prod/bin/cc that detects '-x c++' and calls /opt/SUNWspro/prod/bin/CC instead. 2. The compile proceeds, but dies on lib/Encode/Detect/Detector.c because it's a c++ program, but including perl.h proceeds to include proto.h, which causes the compiler to choke in new and interesting ways: "/opt/csw/lib/perl/5.10.1/CORE/proto.h", line 38: Warning: attribute nonnull is unsupported and will be skipped.. "/opt/csw/lib/perl/5.10.1/CORE/proto.h", line 90: Warning: attribute __malloc__ is unsupported and will be skipped.. "/opt/csw/lib/perl/5.10.1/CORE/proto.h", line 130: Error: "{" expected instead of "(". "/opt/csw/lib/perl/5.10.1/CORE/proto.h", line 139: Error: Linkage specifications are allowed only at file level. "/opt/csw/lib/perl/5.10.1/CORE/proto.h", line 220: Error: "," expected instead of "(". Compilation aborted, too many Error messages. (There were 55 lines of errors, only a sample is shown here.) Some people might switch to gcc for Encode::Detect, but then the resulting compiled object files will not link with the rest of Perl which *was* compiled with the Sun compiler. Anyhoo, some people say this module has been abandoned. I hope not! :-)

Mon Apr 01 17:46:31 2013 JGMYERS [...] cpan.org - Correspondence added

I know of no other way to get a C++ module to build. So unless you have a suggested fix, I'm going to close this out as "rejected".

Mon Apr 01 17:46:32 2013 The RT System itself - Status changed from 'new' to 'open'

Mon Apr 01 18:22:41 2013 pfudd [...] binkmail.com - Correspondence added

Subject:	[rt.cpan.org #84354] Encode::Detect 1.01 assumes gcc
Date:	Mon, 1 Apr 2013 15:22:16 -0700
To:	"JGMYERS via RT" <bug-Encode-Detect [...] rt.cpan.org>
From:	"P Fudd" <pfudd [...] binkmail.com>

Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=84354 > > > I know of no other way to get a C++ module to build. So unless you have

a suggested fix, I'm going to close this out as "rejected". Show quoted text

>

I'm not sure that 'rejected' is the best choice: this is an actual error that will occur to anyone with a perl compiled with the SunPro compiler on Solaris 10. From what I understand, 'rejected' implies that the bug report is a mistake. Perhaps 'open' would be a better choice, since the bug report is not user error? At the very least, other people who will be getting the same error message will look here first and know what's causing it, what's been tried, and what a solution will probably look like. Given that, someone else might have a better idea for fixing it. After all, the problem that Encode::Detect solves is not intimately connected to a feature found nowhere besides the Gnu C++ compiler, right? :-) Thanks

Download cc
application/octet-stream 1.3k

Message body not shown because it is not plain text.