-
Notifications
You must be signed in to change notification settings - Fork 550
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
Compiler desn't work on static-linked installation #52
Comments
From domo@vo.lu[resend: bounced at defender.perl.org wih this lot last time: When I attempt to use perlcc to compile any Perl program, the No definition for sub Fcntl::F_DUPFD Further, if I attempt to compile a program that uses some module with No definition for sub Socket::MSG_PROXY and so on. On reaching the link stage, ld complains /tmp/cc0004921.o(.rw+0xcf70):t.p.c: undefined reference to `XS_Fcntl_constant' and maybe t2.p.o(.rw+0x12ade):t2.p.c: undefined reference to `XS_Socket_pack_sockaddr_in' and so on, and produces no executable. A hacky way round this is to rerun the cc command line produced by Looking at B/C.pm, I see the warnings are coming from and try_autoload() Perl Info
|
From [Unknown Contact. See original ticket]Anyone else seen a duplicate of this problem? I'm building a static Nat
|
From [Unknown Contact. See original ticket]At 21:55 -0700 2000-03-20, Nathan Torkington wrote:
Yes, I see that too. (Static build of RC2 for MachTen 4.1.4.) Byte |
From [Unknown Contact. See original ticket]This ticket, against 5.005_57, can be closed: bleadperl perlcc now |
Migrated from rt.perl.org#854 (status was 'resolved')
Searchable as RT854$
The text was updated successfully, but these errors were encountered: