Control: fixed -1 2.4.0+dfsg-6
Control: tags -1 pending
Thanks for the advice. I've included both Stevens pthread patch, and an
adaptation of my thr_self patch incorporating the feedback. Updated
packaging is available in the Debian GIS git.
Building an updated package is complicated by the fact
Petr Salinger:
Is there any lwpid_t which isn't long and defined by kernel headers?
See upstream sources:
http://svnweb.freebsd.org/base/head/sys/sys/_types.h?revision=255219view=markup
typedef __int32_t __lwpid_t; /* Thread ID (a.k.a. LWP) */
And compare with
I think you can avoid this by using the primitive:
lwpid_t tid;
syscall (SYS_thr_self, tid);
There is a mess in kernel interfaces,
the right one is
long tid;
syscall (SYS_thr_self, tid);
But it holds only for current pthread implementation,
it can be changed anytime.
Petr
Petr Salinger:
I think you can avoid this by using the primitive:
lwpid_t tid;
syscall (SYS_thr_self, tid);
There is a mess in kernel interfaces,
the right one is
long tid;
syscall (SYS_thr_self, tid);
Is there any lwpid_t which isn't long and defined by kernel headers?
--
Robert
Is there any lwpid_t which isn't long and defined by kernel headers?
See upstream sources:
http://svnweb.freebsd.org/base/head/sys/sys/_types.h?revision=255219view=markup
typedef __int32_t __lwpid_t; /* Thread ID (a.k.a. LWP) */
And compare with
Steven Chamberlain:
A workaround may be to use pthread_self(), except that the exported
getCurrentThreadId function has to return 'unsigned int'. On
kfreebsd-amd64 a 64-bit pointer to a pthread_t is not absolutely
guaranteed to be unique if truncated to 32 bits,
I think you can avoid this by
Source: osgearth
Version: 2.4.0+dfsg-5
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Severity: serious
Justification: fails to build from source (but built successfully in the
past)
Hi,
osgearth fails to build on kfreebsd-* because it
Hi Steven,
On 10/04/2013 11:33 PM, Steven Chamberlain wrote:
Hi,
osgearth fails to build on kfreebsd-* because it tries to directly use a
Linux-specific syscall:
https://buildd.debian.org/status/package.php?p=osgearthsuite=sid
cd /«BUILDDIR»/osgearth-2.4.0+dfsg/build/src/osgEarth
osgearth also knows how to use Windows and Mac OS X--specific syscalls
to get a thread ID. This is not portable and there is nothing directly
equivalent on FreeBSD, see:
http://lists.freebsd.org/pipermail/freebsd-hackers/2010-June/031992.html
The FreeBSD equivalent is:
int
9 matches
Mail list logo
