T.R | Title | User | Personal Name | Date | Lines |
---|
1472.1 | | SMURF::DENHAM | Digital UNIX Kernel | Fri Jan 24 1997 17:24 | 12 |
| If you're still coding to the Draft 4 interfaces (pre-V4.0), then
you need to use -threads on V4.0. That gets you the "legacy"
treatment to support the old interfaces.
The legacy layer is in libpthreads.so. The DECthreads "core"
functions, which the legacy layer uses, are in libpthread.so.
If you write a nice up-to-date POSIX.1c program on V4.0, you
build with -pthread, and you'll be linked against libpthread.so.
The libpthread library won't be used.
Hope I've covered the issue. Well, OK for a kernel guy....
|
1472.2 | | DCETHD::BUTENHOF | Dave Butenhof, DECthreads | Mon Jan 27 1997 07:57 | 8 |
| > If you write a nice up-to-date POSIX.1c program on V4.0, you
> build with -pthread, and you'll be linked against libpthread.so.
> The libpthread library won't be used.
Just so nobody gets confused, Jeff meant "The libpthreads library" won't be
used, not "The libpthread library".
/dave
|
1472.3 | Nevermind! Just use the right switch. | WTFN::SCALES | Despair is appropriate and inevitable. | Mon Jan 27 1997 11:01 | 15 |
| .0> Is this still necessary to use if I'm building the project on a UNIX V4.0x
.0> system?
Yes, sadly, using a special switch to instruct the compiler that you are
compiling/linking code for use with threads will probably always be necessary.
.0> Why are there two libraries and which one should I be using - or should I be
.0> using both?
In general, you shouldn't care! As long as you are specifying the correct
switch (either -thread or -pthread, whichever is appropriate), the compiler
(driver) will select the appropriate library or libraries -for- you.
Webb
|