#13201 closed defect (fixed)
dpkg fails to build on Mac OS X 10.5 Leopard
Reported by: | terry@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.5.0 |
Keywords: | Cc: | landonf (Landon Fuller), nox@…, terry@… | |
Port: |
Description
I only use dpkg to get start-stop-daemon which is the very file that fails to build.
Will attach a debug dump.
Attachments (2)
Change History (8)
Changed 17 years ago by terry@…
comment:1 Changed 17 years ago by nox@…
Cc: | landonf@… nox@… terry@… added |
---|---|
Milestone: | → Port Bugs |
Summary: | dpkg fails to build on Leopard → dpkg fails to build on Mac OS X 10.5 Leopard |
comment:2 Changed 17 years ago by terry@…
I've never tried daemondo, sure it will do similar things.
The reason I use start-stop-daemon is that I can then use Debian specific init scripts without change.
Of course I could customize them for all operating systems (and might have to).
Thanks for the suggestion, hoping this can be fixed so I can maintain the same workflow however.
comment:3 Changed 17 years ago by terry@…
There is a bit of code in start-stop-daemon.c that reads:
#include <kvm.h>
If you wrap the kvm.h include as follows, then it seems to compile and run fine.
#if !defined(__ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__) # include <kvm.h> #endif
comment:4 Changed 17 years ago by afb@…
kvm isn't actually used in the "OSDarwin" code path, so the #include <kvm.h> should be disabled.
Note: See
TracTickets for help on using
tickets.
I don't know about start-top-daemon, but isn't it the same thing as daemondo?
Anyway, it seems that someone figure out a fix for this ticket will also fix #13166.