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

Any news on this?
It would be nice to get a fix into a 1.20.1 release.

Also, I looked at the URL
https://buildd.debian.org/fetch.cgi?pkg=gnustep-base&arch=hurd-i386&ver=1.19.3-2&stamp=1273445079&file=log&as=raw

I can't claim to fully understand this log, but I'm guessing it's a build of
a debian source package?
A few queries/observations...

1. Why is LDFLAGS set to "-Wl,-z,defs -Wl,--as-needed" ?  I don't know what
this does ... it seems unlikely (since I guess these flags do no harm on other
systems) but perhaps it's the cause of the problem?  It's a natural suspect
since the flags are for the linker and the problem is a linker issue (the
linker ought to be expecting gnustep_base_user_main to be undefined, not
complaining about it).

2. The base configure log says:
Your gnustep-make is configured to use native objc exceptions, but
the objc runtime does not appear to support setting an uncaught
exception handler.  This means that any uncaught exception will
cause a program to abort immediately.
Consider reconfiguring gnustep-make or updating libobjc to fix this.

So the library is being built with the wrong objective-c library and/or
incorrectly configured gnustep-make.  That suggests that the packages or
package dependencies are faulty.  I can't see how this could have any effect
on the linking issue, but it looks like a package problem.


Of course, this is an old version of GNUstep anyway ... so perhaps this bug
report is obsolete and should simply be closed?



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?29845>

_______________________________________________
  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

Reply via email to