August 2011 - libdispatch-dev - lists.macosforge.org

Lion branch porting status
by Mark Heily 31 Aug '11

31 Aug '11

Just a quick update on the work I've been doing with the Lion branch: As of r30, all of the unit tests compile under Linux. There's a problem with the test harness that prevents 'make check' from running, but I've tried several of the tests individually and they appear to work. Most of the patches are very rough, specific to Linux only, and not ready for submission. I'll polish them up over the next few weeks and start sending them to the list. I've created a compat/ directory and included a private copy of libbsd, libkqueue, libpthread_workqueue, and libMachShims. I wrote libMachShims based on some earlier work porting launchd to Linux. It provides a subset of the Mach headers and emulates some functions like mach_absolute_time(). This avoids the need to sprinkle #ifdefs all around the Mach-specific sections of code. Once things settle down with the libdispatch porting effort, I'd like to take a look at if/how launchd could be combined with libdispatch to serve as a foundation for writing network daemons. Cheers, - Mark

4 6

Lion libdispatch sources posted & next steps for macosforge repo
by Daniel A. Steffen 25 Aug '11

25 Aug '11

The Lion libdispatch sources are now available: http://www.opensource.apple.com/release/mac-os-x-107/ http://www.opensource.apple.com/tarballs/libdispatch/libdispatch-187.5.tar.… The configure/make buildsystem has been updated to produce a working libdispatch.dylib on Lion that can be used/installed in place of the stock version, see INSTALL for details. Next steps are to decide how to integrate the new sources into the macosforge repository; as you will discover, there has been significant refactoring/reorganization, making this not completely trivial. As a first step I was planning to import the Lion source drop on a branch, and then start reorganizing trunk similarly to make trunk changes that are missing from the branch more apparent. Before I get started on that we should make sure that all pending non-controversial patches are integrated onto trunk, does anybody have a list of what is still outstanding? (I guess this is where more consequent use of the trac ticket system on http://libdispatch.macosforge.org/trac/report would be paying off..) Daniel

3 7

Re: [libdispatch-dev] Lion libdispatch sources posted & next steps for macosforge repo
by Daniel A. Steffen 18 Aug '11

18 Aug '11

Thanks, committed with slight amendments for style/whitespace and some simplifications to use existing facilities; in particular on Linux use the main thread as the signal handler thread if it is going to stick around forever anyway rather than spin up a separate signal handler thread from dispatch_main(). Daniel On Aug 17, 2011, at 2:46, Joakim Johansson wrote: > Ooops, reviewing Marks patch it seems he actually integrated the two I submitted as well, so just the ‘linux specific’ ones should be fine (as they weren’t really upon further inspection…) > > So I think just Marks patch cluster from: >> http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000532.html > http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000559.html > > Should be all that is pending... > > Cheers, > > Joakim > > On 17 aug 2011, at 11:43, Joakim Johansson wrote: > >> That’s great news, thanks! >> >> I think a list of outstanding minor patches (submitted after the large Christmas package from Jordan) which are pending would be: >> >> Fixes for a couple of warnings from our statical code analyzer: >> http://lists.macosforge.org/pipermail/libdispatch-dev/2011-May/000529.html >> http://lists.macosforge.org/pipermail/libdispatch-dev/2011-May/000530.html >> >> And a couple of Linux specific ones from Mark Heily: >> http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000532.html >> http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000559.html >> >> Sounds like a very good idea to start using the trac system more consistently going forward… >> >> Cheers, >> >> Joakim >> >> On 16 aug 2011, at 23:32, Daniel A. Steffen wrote: >> >>> The Lion libdispatch sources are now available: >>> http://www.opensource.apple.com/release/mac-os-x-107/ >>> http://www.opensource.apple.com/tarballs/libdispatch/libdispatch-187.5.tar.… >>> >>> The configure/make buildsystem has been updated to produce a working libdispatch.dylib on Lion that can be used/installed in place of the stock version, see INSTALL for details. >>> >>> Next steps are to decide how to integrate the new sources into the macosforge repository; as you will discover, there has been significant refactoring/reorganization, making this not completely trivial. >>> >>> As a first step I was planning to import the Lion source drop on a branch, and then start reorganizing trunk similarly to make trunk changes that are missing from the branch more apparent. >>> >>> Before I get started on that we should make sure that all pending non-controversial patches are integrated onto trunk, does anybody have a list of what is still outstanding? (I guess this is where more consequent use of the trac ticket system on http://libdispatch.macosforge.org/trac/report would be paying off..) >>> >>> Daniel >>> _______________________________________________ >>> libdispatch-dev mailing list >>> libdispatch-dev(a)lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev >> >> _______________________________________________ >> libdispatch-dev mailing list >> libdispatch-dev(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev >

1 0

libdispatch-187.5 (coming soon!)
by Mark Heily 05 Aug '11

05 Aug '11

I just checked out http://opensource.apple.com, and was excited to see the sources for 10.7 have been released. Unfortunately, it was just a tease as the sources for libdispatch are not available yet. I know that there are folks within Apple working on merging the changes from the Apple private branch into the public MacOSforge branch, and I'm wondering how that is going. Would it be possible to get the unmodified libdispatch sources from the 10.7 build so I could try to put together a "portability patchset" that would add the Autoconf stuff and everything needed to build on other platforms? This would probably be easier and faster than having someone at Apple backport the changes from 10.7 into the MacOSforge repo. Think of it as "forward porting" the changes from MacOSforge branch instead of backporting changes the other direction. I believe this is the methodology that OpenSSH has used successfully, where the core OpenSSH team develops strictly for OpenBSD, and a separate team maintains a "portable OpenSSH" branch using a pile of patches that are applied to the upstream releases. As a suggestion, a very kind person from Apple could upload the raw 10.7 sources into the SVN tags directory at this URL: http://svn.macosforge.org/repository/libdispatch/tags/OSX_10_7 Thanks a lot! - Mark

3 2