Re^2: PDL undefined reference to pdl_pthread error on install

[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.

[Don Coyote]

Perl is one of those different things to different people kind of languages, I believe I was probably just expressing a point of view where i couldn't c the wood for the cc's, not trying to detract from PDL at all, merely trying to understand better what perl is and how to use it.

I watched a lecture recently and there was a quote that kind of made sense to me regarding this, their view being that perl could be seen as a compiler for compilers. Unfortunately i cannot recall the identity of the speaker.

I like things working fast so thats great, but i also like understanding how things work, mainly so that im not replicating work uneccessarily.

One of the main areas im tryng to differentiate from is the assembly/machine code/c/perl/xs relations and pipelines and now of course PDL being thrown into the mix. Im sure once I understand what it is that is going on i'll be more relaxed about what im doing.

[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.