New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#line directives in src/pmc confuse Sun's compiler. #1057
Comments
From @doughera88Trying a build with the rakudo "ins" branch today on OpenSolaris/x86 with cd src/pmc && cc -c -I/export/home/doughera/src/parrot/rakudo-ins/parrot/install/include/1.2.0-devel -I/export/home/doughera/src/parrot/rakudo-ins/parrot/install/include/1.2.0-devel/pmc -D_REENTRANT -DPTR_IS_LONG -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHASATTRIBUTE_CONST -DHASATTRIBUTE_FORMAT -DHASATTRIBUTE_MALLOC -DHASATTRIBUTE_NONNULL -DHASATTRIBUTE_NORETURN -DHASATTRIBUTE_PURE -DHASATTRIBUTE_UNUSED -DHAS_GETTEXT -KPIC -g -DHAVE_COMPUTED_GOTO *.c What's happening is this: p6invocation.c starts like this (I've omitted #include "parrot/parrot.h" [ . . . ] #line 1 "./src/pmc/p6invocation.pmc" [ . . . ] #include "pmc_perl6multisub.h" The './src/pmc/' part of the #line directive is what is confusing Sun's compiler. Removing the './src/pmc/' part of the #line directive fixes it. -- |
From @pmichaudOn Fri Jun 12 13:42:59 2009, doughera wrote:
Unfortunately, the #line directives are generated code, so I don't know Can you verify that this is still a problem in the 'ins2' branch? Thanks! Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @doughera88On Fri, 24 Jul 2009, Patrick R. Michaud via RT wrote:
Yes, it's still there. It's the 'cd' at the beginning of this line: cd If memory serves, parrot doesn't change directories like that. Instead, it sets -- |
From @pmichaud
That's a bit of a pain, isn't it? It means we have to explicitly list I guess we'll have to do it that way, but I wish there was something Pm |
From @doughera88On Wed, 29 Jul 2009, Patrick R. Michaud via RT wrote:
Yes, it's a bit of a pain. (Though reasonably automated.) I wonder if it -- |
From @pmichaudOn Wed Jul 29 11:30:10 2009, pmichaud wrote:
Actually, perhaps I'll just create a build/gen_*.pl script that builds Pm |
From @pmichaudOn Wed Jul 29 11:35:17 2009, doughera wrote:
Aha! It does have an option, and I've now updated the ins2 branch to Pm |
From @doughera88Omitting the line numbers worked. This is fixed in the ins2 branch by commit 5d8fc611d2b9b7eacd506f94771b5ba0f7ed8200 Don't generate #line directives in pmc2c output (for Sun compilers). |
From [Unknown Contact. See original ticket]Omitting the line numbers worked. This is fixed in the ins2 branch by commit 5d8fc611d2b9b7eacd506f94771b5ba0f7ed8200 Don't generate #line directives in pmc2c output (for Sun compilers). |
@doughera88 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#66560 (status was 'resolved')
Searchable as RT66560$
The text was updated successfully, but these errors were encountered: