[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-18 Thread Riccardo mottola

Update of bug #30094 (project gnustep):

 Open/Closed: In Test = Closed 

___

Follow-up Comment #10:

The configure seems to work for me on GNU/HURD, GNU/Linux (Debian and
Gentoo), Windows/mingw and FreeBSD 8.0.

I close the bug and will test other platfoms in the coming days (OpenBSD,
Solaris, NetBSD)

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-13 Thread Richard Frith-Macdonald

Follow-up Comment #8, bug #30094 (project gnustep):

I'd like to make a bugfix release of the base library (1.20.1) with all the
recent changes, and this issue is the thing that's holding it up.
I've applied all the latest changes to the stable branch in svn  so that
things can be tried out easily.
Please let me know how you get on.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-13 Thread Yavor Doganov

Follow-up Comment #9, bug #30094 (project gnustep):

Unfortunately I won't be able to confirm that the failure is fixed on
GNU/kFreeBSD until gnustep-base 1.20.x is uploaded to Debian (either with the
upstream fix, or the same as a Debian patch).  It's like a chicken and egg
problem for us...

So do whatever you think is right, and I'll followup later here with the
result.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-12 Thread Richard Frith-Macdonald

Follow-up Comment #7, bug #30094 (project gnustep):

I agree with Yavor that it makes sense to remove all the cruft from our
sourcecode and rely on autoconf to do the hard work for us.  So I've manually
(hope I didn't make any mistake) applied the supplied patch to svn trunk to
let us try it.
If it doesn't work out, we can always revert back.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-11 Thread Yavor Doganov

Follow-up Comment #5, bug #30094 (project gnustep):

Strange, but if that works, OK.

There are 3 more places where this condition needs to be changed, could you
please do that?

GSPThread.h, NSLock.m, NSZone.m

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-11 Thread Riccardo mottola

Follow-up Comment #6, bug #30094 (project gnustep):

I modified the remaining files, it works for me on HURD. Let's keep the bug
in test, for some time so that people have time to build on their machines.

It would be nice if you can arrange a test on kFreeBSD.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-10 Thread Riccardo mottola

Follow-up Comment #2, bug #30094 (project gnustep):

this fix breaks compilation on Solaris again, glibc is a mess, the __GLIBC__
check is not enough and not inconditionally valid.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-10 Thread Riccardo mottola

Update of bug #30094 (project gnustep):

 Open/Closed:  Closed = Open   


___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-10 Thread Riccardo mottola

Update of bug #30094 (project gnustep):

 Open/Closed:Open = In Test

___

Follow-up Comment #4:

added both __GNU__ and __GLIBC__

seems to work on my platfosm.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-09 Thread Yavor Doganov

URL:
  http://savannah.gnu.org/bugs/?30094

 Summary: (Regression) FTBFS on GNU/kFreeBSD: sync.m:87:
error: 'PTHREAD_MUTEX_RECURSIVE' undeclared
 Project: GNUstep
Submitted by: yavor
Submitted on: Wed Jun  9 14:38:36 2010
Category: Base/Foundation
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

1.20.0 fails to build on GNU/kFreeBSD with the following error:

gcc sync.m -c \
  -MMD -MP -Wall -Wdeclaration-after-statement -DGNUSTEP
-DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT
-fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -fno-strict-aliasing
-fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -fgnu-runtime
-fgnu-runtime -fconstant-string-class=NSConstantString
-I../../Headers/Additions -I../. -I../ -I../../Headers -I.
-I/usr/include/GNUstep -I/usr/local/include/GNUstep
-I/usr/local/include/GNUstep -I/usr/include/libxml2 -I/usr/include
-I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/ObjectiveC2.obj/sync.m.o
sync.m: In function 'initLockObject':
sync.m:87: warning: implicit declaration of function
'pthread_mutexattr_settype'
sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared (first use in this
function)
sync.m:87: error: (Each undeclared identifier is reported only once
sync.m:87: error: for each function it appears in.)
make[5]: *** [obj/ObjectiveC2.obj/sync.m.o] Error 1

Trivial patch attached.

GNU libc supports several kernels: Linux, GNU Mach+Hurd, kFreeBSD and
(unofficially) kOpenSolaris.  So the correct check in this case is for the
symbol __GLIBC__, which is guaranteed to be defined on all glibc-based
platforms.  
Perhaps it's worth to leave __linux__ for the rare cases when another libc is
used with Linux (uClibc, dietlibc, etc.), although I'm not sure if the GNUstep
stack works on those systems at all.

Thanks.



___

File Attachments:


---
Date: Wed Jun  9 14:38:36 2010  Name: kfreebsd.patch  Size: 610B   By: yavor

http://savannah.gnu.org/bugs/download.php?file_id=20708

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #30094] (Regression) FTBFS on GNU/kFreeBSD: sync.m:87: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared

2010-06-09 Thread Richard Frith-Macdonald

Update of bug #30094 (project gnustep):

  Status:None = Fixed  
 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

Thanks, I applied that fix.

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?30094

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep