On Dec 9, 2008, at 3:35 PM, Holger Müller wrote:

Hi,

thanks for the quick rely. Don't you use Leopard to verify that?

No, I updated the package and verified that the GUI ran without actually doing a sync.

But I think you are right. I did some googeling and found that statement here This is caused by programs that use the fork() or daemon() function in combination with higher-level APIs. In Leopard you cannot use the CoreFoundation (CF...) APIs on the child side of a fork() without following it with an exec*() function. This has always been true, but Leopard is much more stingy about this kind of thing.
http://discussions.apple.com/thread.jspa?threadID=1209537&tstart=0

Hope someone finds a fix.

Thanks Holger


I have a general idea about what to try--after I get home from work.


2008/12/9 Alexander Hansen <[EMAIL PROTECTED]>

On Dec 9, 2008, at 1:58 PM, Holger Müller wrote:

Hi list! :-)

this is my first message. I am using fink 0.9.0 switched to cvs.
I have installed jpilot 1.6.0-102 and pilot-link 0.12.3-2.

Until now I was not able to sync my Palm m505 on my MacBook using Leopard 10.5.5. In the settings I used "usb:" for the device. If I start JPilot from the terminal and press the sync button in the application I get these messages printed 4 times:

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec(). Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__ () to debug.



The command
> pilot-xfer -p usb: --list

   Listening for incoming connection on usb:... connected!

   Reading list of databases in RAM...

works. Also the command "jpilot-sync" works as expected (syncing my Palm on the console). Only the sync from the JPilot GUI seems to have a problem. I also tried to recompile jpilot without the flock using fcntl (implemented by not setting the compiler switch "USE_FLOCK") did not help.
Does someone have a solution for it?

Thanks Holger




This is the first report I've seen about this issue.

I don't think this is a matter for flock vs fcntl, but rather something specific to how Leopard handles forking. The maintainer for KDE had to put a hack in kdelibs3 to handle a similar error.


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to