perlbug-followup at perl
May 2, 2012, 8:15 PM
On Sat Nov 10 06:22:10 2001, lnett [at] SDSC wrote:
[perl #7895] "Unresolved external" errors from Perl built with bcc5
> I am not sure this is a real bug or just a user problem. I
> have tried a bunch of stuff. The error occurs when
> "miniperl" is building the Makefile for the etc/Sockets
> directory. Here is the error:
> c:\BC5\BIcc32 is not recognized as an external or external
> command, operable program or batch file.
> dmake.exe: Error code 1, while making 'Socket.obj'
> The problem is that miniperl is not building the makefile
> correctly so that CC is defined as c:\BC5\BI*bcc32 where
> "*" is some weird character.
> I tried going into the win32/makefile.mk and removing the
> miniperl part for socket and then correcting all the
> problems in the sockets makefile. But then I get the error:
> Unresolved external '__System__GetTls' referenced from
> module XXV.CPP
> Unresolved external '__isDLL' referenced from module
> Unresolved external '__useDynamicTLS' referenced from module
> The above error comes from the link stage of Socket. I am
> using borland tlink32 for this step....is there something
> else. I ask because miniperl hacks the line that defines the
> linker so I am unable to figure out what to use.
> If I could get miniperl to build the correct makefile I
> think this would resolve these errors. Any
> Laura C. Carrington, Ph.D.
> Scientific Computing Dept. (858) 534-5063 (voice)
> San Diego Supercomputer Center (858) 534-5117 (fax)
> 9500 Gilman Dr. 0505 lnett [at] sdsc
> La Jolla, CA 92093-0505
Gosh, did this ticket fall through the cracks. Thanks for the bug
report, and for volunteering to fix it! It's a shame that no one took up
the offer back in the day.
Unfortunately, eleven years down the line, Perl no longer supports
Borland, so I'm marking this as rejected.
via perlbug: queue: perl5 status: open