Re: Bus error on Mac OS X 10.4

2006-08-10 Thread brian
> [EMAIL PROTECTED] schrieb: >> Open eputil.c >> Jump to line 2065 which should put you right before "#ifdef WIN32". If >> not, move to just before this statement. Add a new line BEFORE it like >> so: >> >> #define __BSD_VISIBLE 1 > > GREAT! > Of course it did, because it a BSD-like Unix. > No pro

Re: Bus error on Mac OS X 10.4

2006-08-10 Thread Frank Wesemann
[EMAIL PROTECTED] schrieb: Open eputil.c Jump to line 2065 which should put you right before "#ifdef WIN32". If not, move to just before this statement. Add a new line BEFORE it like so: #define __BSD_VISIBLE 1 GREAT! Of course it did, because it a BSD-like Unix. You made my day! Thank you ve

Re: Bus error on Mac OS X 10.4

2006-08-10 Thread brian
> Brian schrieb: I have also attached a different file that shows that 'hacks' I had to do to get it to compile. There was a problem with eputil.c and the timezone variable. It's the same fix that was implemented for FreeBSD, just has to be implemented for Mac OS X as well

Re: Bus error on Mac OS X 10.4

2006-08-10 Thread Frank Wesemann
Brian schrieb: I have also attached a different file that shows that 'hacks' I had to do to get it to compile. There was a problem with eputil.c and the timezone variable. It's the same fix that was implemented for FreeBSD, just has to be implemented for Mac OS X as well. The changes I made are

Re: Stop processing without generating an error message

2006-08-10 Thread Gunnar Wolf
Gerald Richter dijo [Thu, Aug 10, 2006 at 06:44:38AM +0200]: > > [Thu Aug 10 01:08:22 2006] [error] [19700]ERR: 24: Error in > > Perl code: component at > > /home/gwolf/cvs/comas/trunk/embperl/base.pm line 156, > > line 4.\n > > Which is line 156 in base.pm. Is it the exit 0, or is it a diff