PDL undefined reference to pdl_pthread error on install

[Don Coyote]

Fail point in build log

g++ Core.def -o ..\..\blib\arch\auto\PDL\Core\Core.dll -mdll -s -L"C:\
+Dwimperl\perl\lib\CORE" -L"C:\Dwimperl\c\lib" ... pdlutil.o "lib.a" x
+<i>n</i> -Wl,--enable-auto-image-base

pdlutil.o:pdlutil.c:(.text+0x1f76): undefined reference to `pdl_pthrea
+d_realloc_vsnprintf'
pdlutil.o:pdlutil.c:(.text+0x4c): undefined reference to `pdl_pthread_
+free'
collect2: ld returned 1 exit status
dmake:  Error code 129, while making '..\..\blib\arch\auto\PDL\Core\Co
+re.dll'
dmake:  Error code 255, while making 'subdirs'
dmake.exe:  Error code 255, while making 'subdirs'
-> FAIL Installing PDL failed.

h tihere57!

using cpanm PDL failed here. Also tried cpan PDL, but that did not even want to connect to strawberryperl website, and failed before it started.

Not sure I could even go in and comment these out, as its being auto-installed from cpan.

background: tk is way too slow at gfx, maybe SDL will be faster. Reading the Manual, want to intereact iwith my gfx capapbilities if possile. I did do a bit of blitting a while back at the suggestion of an esteemed perlmonk. Hearing the screams rising up from the pits of hell is probably best listened to only once though. OpenGL wont install on usb, so its gotta be PDL, for now.

---

^DeCoy

[Athanasius]

Hello Don Coyote,

Since you mention Strawberry Perl: you should note that they have a number of “PDL editions” which install PDL along with Perl. These should work out of the box. See https://strawberryperl.com/releases.html.

Hope that helps,

[Don Coyote]

Hello Athanasius

Yes, I may do well to do so. The version I was installing to is Dwimperl from a Padre install. Perhaps my Toolbox can use a PDL shaped strawberry also, at least until I can weild them one in each hand or the like.

Assuming that works it would make sense, nothing ever seems to work out-of-the-box recently, or ever. Apart from that good ol' version I downloaded 800 yrs ago, lol. Which is why I hadnt considered to just download a ready to go PDL version.

I am only just starting to peek at c code on text files, while away from debugging that stuff just yet. Have discovered a bash emulator and Scape Codes, so the Camel starting to make a little more sense, even if i still cant use all the builtins.

I would really like to be able start compiling versions rather than dl pre-compiled binaries, but I may not be so far off that.

Ty for the hint

[etj]

When reporting this kind of thing, it's very helpful (and really, essential) to include the output of perl -V.

But I agree with Athanasius that a much better way forward is to start with the latest Strawberry Perl PDL edition. If the PDL that comes with it isn't the latest and shiniest one, you are more or less guaranteed to be able to update its PDL with cpanm. If not, please report that on PerlMonks, or open a GitHub issue (or send email to one of the mailing lists, or join the IRC channel).

[Don Coyote]

Hello etj

I can see that would be more help, thank you for saying.

The Version is iirc a 5.14.2 as part of a pre-compiled Padre install. That install itself uses or locates itself within a Dwimperl in my user hieararchy so yes it is all a little bit confused.

I am presently attempting to cleanthrough my system and update/migrate to something that I have better control over in terms of versions.

My comprehension of building and installing is still novice, but getting clearer. At least if its c, here all the installs worked with the gcc lines, but just tripped up with the g++ line.

It seems as most of installing is all about location and linking, and versioning is a significant aspect of this.

I have the dread that the underlying issue will probably not resolve with using PDL, so I just wanted to confirm for reassurance and avoid unnecessarily learning yet another UI.

One of the factors for choosing Perl was that everyone has said how you can easily see what you are doing, until you realise that the people who are saying this are all mainly just using Perl to aid writing their c.

For an intermediate user of perl such as myself it can come across as fairly opaque, portable pre-compiled binaries are great for usage, but still really dont help when you want to hack and see whats going on as a learning exercise.

I suppose one thing I would like strawberry to provide are some binaries with a few more -D flags options included, specifically -DDEBUG, but more would be nice, essentially a version that has all the -DDEBUG set, so should I find myself within an environment that has the tools to do so I could maybe investigate what is going on.

I also am aware that it may be decision already made due to the quite likely possibility of user accidentally destroying their system or such as to why they do not do so.

In which case I should probably try to follow manually an automatic install of something like the perldoc or pod modules. As it seems most versions of perl, uxpecially when shipped as part of larger or other dist (term emus, textual apps, os dists, ... ), dont appear to include this, most basic and valuable source of information. Mind you, you would be lucky if they ship with man or info either... lol

---

Just looking for that one nugget of knowledge that makes everything make sensei

[etj]

Belatedly...

One of the factors for choosing Perl was that everyone has said how you can easily see what you are doing, until you realise that the people who are saying this are all mainly just using Perl to aid writing their c.

I don't think there are many people who "mainly just (use) Perl to aid writing their c". Speaking as maintainer of PDL, which according to me is the most exaggerated Perl-to-write-C environment that exists, the aim of at least PDL is to enable writing Perl things that run Really Fast. In other words, the Perl in PDL is to enable Perl, just utilising C to do so (just like Perl itself which is written in C).

If you know differently, I'd be highly interested to hear about it.

[etj]

Nothing is stopping you from building your own Perl, and setting in that whatever flags you like. A way to make that easier on Windows might be to try https://github.com/dnmfarrell/berrybrew.