Skip to content
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

perlcc code compiles but won't run: WHY???? #94

Closed
p5pRT opened this issue Jun 22, 1999 · 3 comments
Closed

perlcc code compiles but won't run: WHY???? #94

p5pRT opened this issue Jun 22, 1999 · 3 comments

Comments

@p5pRT
Copy link

p5pRT commented Jun 22, 1999

Migrated from rt.perl.org#898 (status was 'resolved')

Searchable as RT898$

@p5pRT
Copy link
Author

p5pRT commented Jun 22, 1999

From The RT System itself

I've spent three days looking through online documents and I can't
find anything that even gives me a clue as to how to solve my Perl
problem. Can someone PLEASE help, or at least tell me the best place
to look (yes, I've been all through CPAN).

Specifically, my problem is this​:

I just started attempting to use perlcc with Redhat Linux 5.2 on an
Intel platform (Pentium 133). My perl code seems to compile okay using
perlcc, but it won't run. What is SEEMS to be choking on is
subroutine calls, even though it tells me the syntax of my code
was okay during the compile phase. What I get when I run my code
is a "segmentation fault" and a core dump. Note​: I am NOT using any
modules and I have tested the problem by using a simple program which
does nothing except call a subroutine which prints "hello world".
If I had written this in fortran, I would think this is some kind of
link error, but Perl doesn't link, does it?

HELP PLEASE!

Rick Johnson
firespring@​nfx.net

Rick Johnson <firespring@​nfx.net>

@amcareem
Copy link

One of the oldest problems. Can anyone say like what would has caused this problem? Just curious to know

@jkeenan
Copy link
Contributor

jkeenan commented Aug 30, 2021

One of the oldest problems. Can anyone say like what would has caused this problem? Just curious to know

Please note that this problem was marked Resolved way back in 2003 when the ticket was being tracked in RT. Indeed, the original filing date suggests that this ticket may have been filed even before we moved to RT. The original poster does not provide sufficient detail for someone to understand the problem and never followed up. That is probably the reason the ticket was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants