Re: [Mingw-users] missing pthreadGC2.dll

[Charles W. <cwi...@us...>]

On 9/15/2010 9:51 PM, Thomas Sharpless wrote:
> Thanks, Chuck
> 
> The installs you recommended got pthread.h, sched.h and libpthread_2.dll
> OK.  But I don't see a new semaphore.h -- do I need to install another
> package to get that?

No.  It is in that package:

$ tar tJf
../var/cache/mingw-get/packages/pthreads-w32-2.8.0-3-mingw32-dev.tar.lzma
include/
include/pthread.h
include/sched.h
include/semaphore.h   <<<<< right here.
lib/
lib/libpthread.dll.a

If semaphore.h didn't get unpacked, I'd check
<installation_root>/var/cache/mingw-get/packages/ and verify the
tarball, as I've done above.

I'm going to assume that "libpthread_2.dll" was a typo; the file is:

$ tar tJf
../var/cache/mingw-get/packages/libpthread-2.8.0-3-mingw32-dll-2.tar.lzma
bin/libpthread-2.dll


> The old headers are in c:/mingw/mingw32/include, while the new ones went
> into c:/mingw/include.  Likewise for the import lib.  Has there been a
> change in the official directory structure? 

Yes, there has.  In that very early prototype version, the basic runtime
support stuff was put into the ${prefix}/${host}/{include,lib}
directories, where on MinGW, prefix is usually C:\MinGW, and $host was
defined as the alias "mingw32" instead of the fully qualified platform
triple "i686-pc-mingw32".

However, in the new releases, everything goes into
${prefix}/{include,lib} just like on unix.

> The mingw that came with my Qt
> 4.6 -- which I have not touched -- has the old arrangement, and no pthreads
> dll (but of course Qt wouldn't need that).

I don't mean to be rude, but we really can't support anything -- even if
it calls itself "mingw" -- that is distributed by somebody else.  We
have no idea what they have done...

> I'm still rather in the dark about mingw-get.  Is there a good
> human-readable list of the MinGW packages and what they contain? 

Well, not as such, no.  However the manifests themselves are just XML
files, and are in plain english.  Take a look here:

https://sourceforge.net/projects/mingw/files_beta/Automated%20MinGW%20Installer/mingw-get/catalogue/

OR, install a new MinGW/MSYS somewhere using mingw-get-inst, and look in
<installation_root>/var/lib/mingw-get/data/   All the .xml manifests
live there (ignore the ones whose names contain bunch of hex digits).

One of the primary goals for mingw-get in the short- to medium-term is
to add 'mingw-get show' (or list, or search, or something like that)
that can do what you ask.  Patches Thoughtfully Considered.

> And what
> are the preconditions for using it to update Msys?

It's best if you don't try to use mingw-get to "update" anything that
wasn't originally INSTALLED by mingw-get.  You're better off starting
"fresh" with a new mingw-get-created installation.

> BTW I ran into a nasty little problem ...

Ignoring this bit, as you've already found an alternate solution.

--
Chuck