Sorry to tell you, but it is part of GeekGadgets (Alpha)
ftp://ftp.geekgadgets.org/pub/geekgadgets/amiga/m68k/alpha/pth/

even 1.4.1

Have you tried version 2.0.0+?

http://www.ossp.org/pkg/lib/pth/

There are also the development snapshots: ftp://ftp.ossp.org/pkg/lib/pth/

PS: Could a moderator edit the link to http://www.whoosh777.pwp.blueyonder.co.uk/pthreads.html

_________________
Best regards,
hnl_dk - Henning Nielsen Lund [Denmark]

Please send no PM to me, email me if you want to contact me. See you somewhere else.

Hope you get your RPM port to work (including db)

_________________
Best regards,
hnl_dk - Henning Nielsen Lund [Denmark]

Please send no PM to me, email me if you want to contact me. See you somewhere else.

@hnl_dk said:

=========================================================

Sorry to tell you, but it is part of GeekGadgets (Alpha)
ftp://ftp.geekgadgets.org/pub/geekgadgets/amiga/m68k/alpha/pth/

even 1.4.1

======================================================


ok, but why is it in the alpha directory?


In fact why are they all alpha?


Whats the point of porting a new version when the previous
version never left alpha?


Thats like failing the exams and moving on nonetheless to the
next grade!


rpm4.0 is in the Geek alpha directory and it totally malfunctions,
thats why I did my own port. Its also why I now ignore the alpha
directory,


The configure for this port is *very* tricky, has maybe 10 different
bugs which trip up all over the place on AmigaOS,
there is also a bug in a Geekgadgets include file which will sink a port.
Thats why the port took 1 day instead of say 1/2 hour which libbz2.a took.


If the port passes all the example test programs which my port
has then it should never have entered the alpha directory.


You can verify for yourself that my port is not an alpha by
trying 7 of the test programs in
http://www.whoosh777.pwp.blueyonder.co.uk/threaded_68kprograms.lha,


:test_std is the important test.


I can upload the remaining 2 test programs also: test_select
which doesnt do very much and test_sfio which is irrelevant as
I havent compiled in sfio.


Now OTOH with the pre-emptive version of libpthread.a which I attempted
*all* the supplied test programs failed, so that attempted port would be in
the alpha directory.


==============================================================

Have you tried version 2.0.0+?

http://www.ossp.org/pkg/lib/pth/

There are also the development snapshots: ftp://ftp.ossp.org/pkg/lib/pth/

====================================================


Didnt know it existed, I visited the only link I found and 1.4.0
was the latest version. When time permits I may attempt this,
for the moment I think the current port is probably quite adequate.
Keeping up with version numbers is a treadmill. IMO one should only
keep up with version numbers out of necessity eg rpm4.#? needed to
be done because rpm3 and earlier will not extract from current
#?.rpm files.


All I know is that my port is fully functioning, all test example
programs function, so it would never enter an alpha directory,


my attempt at pre-emptive libpthread.a OTOH would be in an alpha directory
and also would be quite useless. I will make one last attempt to
port it tonight, and then I am moving on to other projects.


BTW how come no-one pointed me to pth when I ported rpm4.0 and
said that I need libpthread.a to do a full port?


Re: db, when I have some spare time I may try to do a full port of rpm4.0,
however IMO the db facility is an irrelevant gimmick on AmigaOS.
On Linux you probably need the db facility because Linux is so
humungously bloated that its a full time job keeping it maintained.


whoosh

Have answered on A.org

_________________
Best regards,
hnl_dk - Henning Nielsen Lund [Denmark]

Please send no PM to me, email me if you want to contact me. See you somewhere else.

the moment the material promised in:

http://hyperion-entertainment.com/_amiga/news_031225b.html

is bundled with all A1s I will be reaching for my cheque book,
for me at least OS4 would be as good as released,

with such developer material I can then start on various ambitious
projects which would be too time consuming to even think about
on a 68030. I can also begin generating G3 native programs,
I will also generate 68k material via my existing GG setup,

its also going to be fun to play around with the new h/w

a pre-release or ongoing public beta is the best approach
because you "catch" all the real criticisms before they
"happen",

see in this thread how I caught that 2.0.0 is the version
of pth to port, I would never have even determined that it existed
from where I was standing.

Similarly with a past pre-release I had my knuckles rapped for using
gcc.2.7.2, I was literally ordered to use gcc-2.95.3-4, how dare you
compile this with gcc.2.7.2!

so perhaps a week later I was using Geekgadgets for the first time,
with gcc-2.95.3-4 and wondering about the other criticisms,

and when I did the actual release the response was so muted,
because all the criticisms had been blown at pre-release time!

private beta people will always be afraid of frank criticism
because they may be removed from the beta list,

criticism hurts, but its just for a moment and then
life goes on, and you gradually respond to the criticisms
one by one. Once the criticisms subside things tend to
become very dynamic,

also with the above material money starts to flow in,
and programmers begin on projects,

The important thing is that the OS3.1 filesystem is in its
final form, it doesnt matter if the graphics or sound crashes
it does if the filesystem malfunctions. To this day I use
FFS because it is so reliable. (If I lose even 1 byte from a
file system I get really annoyed and begin removing said filesystem,
but I will happily endure a dozen screen crashes in a row.)

:with a release ready OS3.1 filesystem existing owners can connect
their existing drives into the new machines and know everything is safe,
any OS4 specific filesystem developments neednt be release ready but the
OS3.1 filesystem must be release ready, nothing else in the OS needs
to be release ready.


Major changes of direction for the OS4 project should happen
within a few days of such material reaching the public,


They have made a wise choice of gcc,
I hope its gcc-2.95.3-4 because that is very stable and
exists across the board (its what I currently use for 68k).


I think maybe they should gradually create + release on an ongoing
basis the above promised material from a website in parallel to
eventually sending out complete CDs. It will reduce the time lag,
people can then also download the material in an ongoing way.

via webstats they can then also know which are the popular bits,
which in turn can affect the project direction. eg if lots of
people are downloading graphics autodocs and noone downloading
sound autodocs, then it means they should focus on the graphics,