January 2008 - macports-dev - lists.macosforge.org

Re: [33525] trunk/dports/python/py25-gsl/Portfile
by William Siegrist 30 Jan '08

30 Jan '08

I dont need the ticket, but feel free to file one in server/hosting if you want to move the discussion there. I should be able to get this setup tomorrow. Thanks for the "--maintainer", I figured there was a better way, and also the "-q" since I had noticed the exit status issue and was going to also do some grepping for that. -Bill On Jan 29, 2008, at 7:21 PM, Ryan Schmidt wrote: > On Jan 29, 2008, at 12:59, William Siegrist wrote: > >> On Jan 29, 2008, at 6:29 AM, Ryan Schmidt wrote: >> >>> * "port lint" should be run by the Subversion repository in a post- >>> commit hook and any problems found emailed to the committer and >>> the maintainer: >>> >>> http://trac.macosforge.org/projects/macports/ticket/12594#comment:4 >> >> I can add `port lint` to the post-commit for any Portfiles if you >> want. > > That would be great. Should I file you a ticket for that? > >> I dont see a way to get only the list of maintainers from port, but >> I can always grep/regexp to get them from `port info`? I seem to >> remember a better way though. > > Get the port's maintainers (comma-space separated) like this: > > port -q info --maintainer $PORT > > Then you'll have to filter that to exclude nomaintainer(a)macports.org > and openmaintainer(a)macports.org. > > `port lint` currently always exits with status 0, even if it finds > something wrong with the portfile. This is unfortunate. However, an > acceptable workaround for now would be to run: > > port -q lint $PORT > > This will only produce output if there are problems in the port. And > only in that case should the email be sent. > ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist(a)apple.com 408 862 7337

1 0

Poppler won't build on Mac OS X 10.3.9
by Stephen Williams 30 Jan '08

30 Jan '08

There are trak items for this issue but it seems to be setting fallow for a while and this is leaving me unable to install gimp. Has anybody any clue how to work around poppler not building so that I can get on with trying to install gimp on my Mac? -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."

1 0

Re: [33525] trunk/dports/python/py25-gsl/Portfile
by Ryan Schmidt 29 Jan '08

29 Jan '08

On Jan 29, 2008, at 01:21, jmpp(a)macports.org wrote: > Revision: 33525 > http://trac.macosforge.org/projects/macports/changeset/33525 > Author: jmpp(a)macports.org > Date: 2008-01-28 23:21:25 -0800 (Mon, 28 Jan 2008) > > Log Message: > ----------- > > Change portname to py25-gsl, as it should have been from the start. > > To all committers: when using a given port as the basis of a new > one, please always remember to make sure > you adapt the portname for the latter, as having duplicate portname > entries in our tree is not allowed > (not only does it mess up informational operations, but it could > also wreck havoc for a user that somehow > manages to install the two colliding ports). > > Yes, I'm aware we don't have strong checks against this harmful > situation within MacPorts' base, and I'm also > aware that we should... But, as we currently don't, let warnings > like this raise committers' awareness of the > issue, while we develop a *real* solution. Yeah. A good solution would already be: * "port lint" should issue a warning for this: http://trac.macosforge.org/projects/macports/ticket/13263 * "port lint" should be run by the Subversion repository in a post- commit hook and any problems found emailed to the committer and the maintainer: http://trac.macosforge.org/projects/macports/ticket/12594#comment:4

2 1

Re: [33538] trunk/dports/science/molden/Portfile
by Ryan Schmidt 29 Jan '08

29 Jan '08

On Jan 29, 2008, at 08:21, jochen(a)macports.org wrote: > -destroot { cd ${workpath}/${distname} > - system "cp molden ${destroot}${prefix}/bin" > - } > +destroot { system "install -c -m 755 ${workpath}/$ > {distname}/molden ${destroot}${prefix}/bin/" } Removing the "cd" command is good, but really you should use the Tcl xinstall command, not shell out to the install command using system. This should do it: xinstall -W ${worksrcpath} molden ${destroot}${prefix}/bin

3 2

Re: [33536] trunk/dports/sysutils/beanstalkd/Portfile
by Ryan Schmidt 29 Jan '08

29 Jan '08

On Jan 29, 2008, at 07:29, brett(a)macports.org wrote: > Revision: 33536 > http://trac.macosforge.org/projects/macports/changeset/33536 > Author: brett(a)macports.org > Date: 2008-01-29 05:29:47 -0800 (Tue, 29 Jan 2008) > > Log Message: > ----------- > and fix portfile for new location > > Modified Paths: > -------------- > trunk/dports/sysutils/beanstalkd/Portfile > > Modified: trunk/dports/sysutils/beanstalkd/Portfile > =================================================================== > --- trunk/dports/sysutils/beanstalkd/Portfile 2008-01-29 13:20:28 > UTC (rev 33535) > +++ trunk/dports/sysutils/beanstalkd/Portfile 2008-01-29 13:29:47 > UTC (rev 33536) > @@ -22,7 +22,7 @@ > port:gmake > > use_configure no > -patchfiles patch-Makefile > +patchfiles files/patch-Makefile > patch.pre_args -p1 > post-patch { > reinplace "s|__PREFIX__|${prefix}|g" ${worksrcpath}/Makefile No, that's not correct; this gives you: $ sudo port install beanstalkd Password: ---> Fetching beanstalkd ---> Attempting to fetch files/patch-Makefile from http:// svn.macports.org/repository/macports/distfiles/beanstalkd ---> Attempting to fetch files/patch-Makefile from http:// svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch files/patch-Makefile from http:// svn.macports.org/repository/macports/downloads/beanstalkd Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. $ This revision should be reverted. The "files" directory is the location in which patchfiles are looked for. The directive "patchfiles patch-Makefile" was already correct.

1 0

platform range and set arguments?
by Jordan K. Hubbard 28 Jan '08

28 Jan '08

Hey all, I was just looking at the ghc port a few days ago, mostly in an attempt to figure out why it a-splode! on my 10.5 PPC system, and I noticed a lot of this: platform darwin 7 powerpc { ... } platform darwin 8 powerpc { ... } platform darwin 8 i386 { ... } And so on. It occurred to me that if "platform darwin 9 powerpc" (that's me) was going to duplicate a lot of the existing rules, maybe it would make more sense to introduce ranges and sets to the existing logic (I checked, and there's currently no support for it that a cursory glance indicated, anyway). Then we could do stuff like this: platform darwin [7-8] powerpc { ... } platform darwin 9 {powerpc, i386} { .. } And have far more concise portfiles. We might also have a platform_isset procedure so that you could do: platform darwin [7-9] { if {[platform_isset darwin 8]} { .. do some special tiger-only magic .. } ... more darwin generic foo here ... } Thoughts? If folks like the idea and nobody immediately jumps to do it, I might give the appropriate hacks a whack (eee! managers coding!). - Jordan

4 4

PortIndex Regen Failure on Saturday 2008-01-26 at 15:30:00
by mp-user＠geeklair.net 28 Jan '08

28 Jan '08

checking build system type... powerpc-apple-darwin9.1.0 checking host system type... powerpc-apple-darwin9.1.0 checking target system type... powerpc-apple-darwin9.1.0 checking for sw_vers... sw_vers checking Mac OS X version... 10.5.1 checking Xcode version... 3.0 checking MacPorts version... 1.6.0 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for gcc... gcc checking whether we are using the GNU Objective C compiler... yes checking whether gcc accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... yes checking whether ln -s works... yes checking for mtree... /usr/sbin/mtree checking for cvs... /usr/bin/cvs checking for svn... /usr/bin/svn checking for rsync... /usr/bin/rsync checking for sed... /usr/bin/sed checking for tar... /usr/bin/tar checking for make... /usr/bin/make checking for launchd... no checking for launchctl... /bin/launchctl checking for xcodebuild... /usr/bin/xcodebuild checking for gnutar... /usr/bin/gnutar checking for gnumake... /usr/bin/gnumake checking for bzip2... /usr/bin/bzip2 checking for xar... /usr/bin/xar checking for open... /usr/bin/open checking for sed... (cached) /usr/bin/sed checking which sed flag to use for extended regexp... -E (BSD) checking for tar... (cached) /usr/bin/tar checking for gnutar... (cached) /usr/bin/gnutar checking for which tar variant to use... /usr/bin/gnutar checking for /usr/bin/gnutar --no-same-owner support... yes checking how to mark unused variables... checking for gcc symbol visibility attribute... __attribute__((visibility("hidden"))) checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... -D_THREAD_SAFE checking how to run the Objective C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... rm: conftest.dSYM: is a directory rm: conftest.dSYM: is a directory yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking objc/objc.h usability... yes checking objc/objc.h presence... yes checking for objc/objc.h... yes checking if linking libobjc requires pthreads... no checking for Apple Objective-C runtime... yes checking for GNU Objective C runtime... no configure: Using Apple Objective-C runtime checking for Apple Foundation library... yes configure: WARNING: GNUSTEP_SYSTEM_ROOT is not defined in your environment, preventing the use of GNUstep's Foundation library configure: Using Apple Foundation library checking for CoreFoundation framework... yes checking for SystemConfiguration framework... yes checking for IOKit framework... yes checking for CFNotificationCenterGetDarwinNotifyCenter... yes checking for whether we will build daemondo... yes checking for ports tree... configure: WARNING: No ports tree found checking for MacPorts config directory... ${sysconfdir}/macports checking for install user... mp-user checking for install group... mp-user checking what permissions to use for installation directories... 0755 checking how to run the C preprocessor... gcc -E checking for ANSI C header files... (cached) yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for sys/wait.h that is POSIX.1 compatible... yes checking whether stat file-mode macros are broken... no checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking paths.h usability... yes checking paths.h presence... yes checking for paths.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking crt_externs.h usability... yes checking crt_externs.h presence... yes checking for crt_externs.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking sys/fcntl.h usability... yes checking sys/fcntl.h presence... yes checking for sys/fcntl.h... yes checking sys/cdefs.h usability... yes checking sys/cdefs.h presence... yes checking for sys/cdefs.h... yes checking err.h usability... yes checking err.h presence... yes checking for err.h... yes checking libgen.h usability... yes checking libgen.h presence... yes checking for libgen.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking readline/readline.h usability... yes checking readline/readline.h presence... yes checking for readline/readline.h... yes checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking sys/paths.h usability... yes checking sys/paths.h presence... yes checking for sys/paths.h... yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking whether closedir returns void... no checking for pid_t... yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... no checking for bzero... yes checking for memset... yes checking for dup2... yes checking for regcomp... yes checking for strdup... yes checking for strerror... yes checking for strtol... yes checking for fgetln... yes checking for lockf... yes checking for flock... yes checking for setmode... yes checking for strcasecmp... yes checking for strncasecmp... yes checking for strlcpy... yes checking for copyfile... yes checking if readlink conforms to POSIX 1003.1a... yes checking for MD5Update in -lmd... no checking for MD5_Update in -lcrypto... yes checking openssl/md5.h usability... yes checking openssl/md5.h presence... yes checking for openssl/md5.h... yes checking for X... no checking for XOpenDisplay in -lX11... yes Please install the X11 SDK packages from the Xcode Developer Tools CD configure: error: Broken X11 install. No X11 headers ./configure script failed.

5 8

Re: Website localization
by Thomas de Grivel 28 Jan '08

28 Jan '08

2008/1/27, Ryan Schmidt <ryandesign(a)macports.org>: > > On Jan 26, 2008, at 18:21, Juan Manuel Palacios wrote: > > > On Jan 25, 2008, at 3:30 PM, Tetsuya Wada wrote: > > > >> Thank you for providing us the MacPorts. I'm building one of my > >> Mac mini as a home server. It couldn't be made without the site. > >> Since the site is so useful, it would be so nice if the site has > >> Japanese. I'm sure many Japanese users are interested, also. > >> > >> Do you have any plan to publish the site with Japanese as well? If > >> I could contribute the Japanese translation, it is my pleasure. > > > > > > I think it would be great to start localizing our new website, > > even though at the moment we currently don't have any structured > > plans for it. I guess it's a great moment to start putting them > > together ;-) > > > > If you're acquainted with subversion and our source repository I'd > > recommend checking out the trunk/www directory, which is where the > > website sources live. Have a look at the files there and give it a > > try translating into Japanese the main section files, like > > contact.php , index.php, install.php and ports.php, in utf-8 format > > please. There are others that you'll need to have a fully > > functional Japanese website, but those will have to be sorted out > > as we put together the new localization structure within trunk/www > > (there's trunk/www/localized already, but it's sorely outdated, so > > don't waste any time looking into that). > > > > When you have that initial set of files ready, please submit them > > as attachments to an appropriate ticket filed under our "Website & > > Documentation" milestone (http://guide.macports.org/ > > #project.tickets & http://trac.macports.org/projects/macports/ > > newticket). I'll suggest a localization hierarchy as I give them a > > try on my local web server. > > I'm in favor of having our web site localized. However, I don't think > we're at the point where we can start soliciting translations yet. > Before a web site can be localized (translated into different > languages), it must be internationalized (engineered so that it can > be localized). And our web site is very much not. The few times I > have looked at the web site source, it has struck me that logic and > presentation and user-visible strings are all mixed together which > does not lend itself to internationalization. I was going to suggest > (and forgot before, so I'm mentioning it now) that we remove the > pretty flag flyout menu from the upper right of the site since it > doesn't do anything, and can't, until we internationalize. > > While working at a web site programming company in Germany for 3 > years, internationalization was one of my specialties. I researched > available options and we ended up using a PHP-reimplementation of > gettext in our projects, which I wrote. Message catalogs were edited > with POEdit. We also had libraries of functions for dealing with > internationalized representations of dates, times and currency. I'll > be happy to help internationalize the MacPorts web site. However I > fear we need some more work before we can start that. > > We currently have separate looks and separate code for > www.macports.org, guide.macports.org, db.macports.org and > trac.macports.org. I would very much like all of this content to have > a unified appearance and sensible unified URLs under > www.macports.org. This is of course difficult since www.macports.org > is PHP, guide.macports.org is XML, db.macports.org is Ruby, and > trac.macports.org is Python. Trac can probably be skinned; I'll have > to read the docs. XML can be restyled with a different XSLT and CSS. > The main web site can be rewritten. As for the MacPorts DB, I still > struggle to understand its purpose and its relationship with the > Available Ports page. Can someone clarify this for me? > > Recently I have been interested in the Zend Framework. It is a > framework for writing PHP web sites, and yes, there are a zillion > other frameworks out there, but the Zend Framework has the distinct > advantage of having been written by the same people who wrote the PHP > language. I watched the tutorial videos and it seems reasonable. It > includes components for DB access using PDO (something else we should > be using but aren't), and for localization using gettext or several > other apparently standard methods (though I haven't tried using these > components yet). I think it would be good if www.macports.org were > written to use the Zend Framework. I intend to put together a small > unrelated web site using Zend Framework to see how it works. Then it > might be nice to sit down and work out what exactly the site map for > the MacPorts web experience is. And from that maybe a new > internationalized web site can emerge. Sorry for interfering in this discussion but I must object that in a modern website you ought to separate infrastructure and content, because both always change and could always be further improved (and will be hopefully). However if you wait one to be finished to start the other you will cripple yourself badly because none of them will ever be finished. I assume some translated copy of the site could be made available rather simply and when the time comes it could be merged into the new optimized infrastructure. Well.. that's just suggestion as I can't do much more right now (I might contribute to some ports soon enough though ; ) . Hope it helps, regards, -- Thomas de Grivel

1 0

Re: [33483] trunk/base/src/port1.0/portconfigure.tcl
by Ryan Schmidt 28 Jan '08

28 Jan '08

On Jan 27, 2008, at 14:40, afb(a)macports.org wrote: > Revision: 33483 > http://trac.macosforge.org/projects/macports/changeset/33483 > Author: afb(a)macports.org > Date: 2008-01-27 12:40:10 -0800 (Sun, 27 Jan 2008) > > Log Message: > ----------- > set canonical system name, for universal configure > > Modified Paths: > -------------- > trunk/base/src/port1.0/portconfigure.tcl > > Modified: trunk/base/src/port1.0/portconfigure.tcl > =================================================================== > --- trunk/base/src/port1.0/portconfigure.tcl 2008-01-27 20:32:06 > UTC (rev 33482) > +++ trunk/base/src/port1.0/portconfigure.tcl 2008-01-27 20:40:10 > UTC (rev 33483) > @@ -116,9 +116,23 @@ > ui_msg "$UI_PREFIX [format [msgcat::mc "Configuring %s"] > [option portname]]" > } > > +# internal function to determine canonical system name for configure > +proc configure_get_universal_system_name {args} { > + global configure.universal_target > + switch -- ${configure.universal_target} { > + "10.4" { return "i686-apple-darwin8" } > + "10.5" { return "i686-apple-darwin9" } > + } > + return "" > +} > + > # internal function to determine the universal args for configure.cmd > proc configure_get_universal_args {args} { > + set system [configure_get_universal_system_name] > set params "--disable-dependency-tracking" > + if {[info exists system] && $system != ""} { > + set params "$params --host=${system} --target=${system}" > + } > return $params > } This works on PowerPC Macs too? What problem does this solve? Just curious.

2 1

PortIndex Regen Failure on Monday 2008-01-28 at 03:30:00
by mp-user＠geeklair.net 28 Jan '08

28 Jan '08

checking build system type... powerpc-apple-darwin9.1.0 checking host system type... powerpc-apple-darwin9.1.0 checking target system type... powerpc-apple-darwin9.1.0 checking for sw_vers... sw_vers checking Mac OS X version... 10.5.1 checking Xcode version... 3.0 checking MacPorts version... 1.6.0 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for gcc... gcc checking whether we are using the GNU Objective C compiler... yes checking whether gcc accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... yes checking whether ln -s works... yes checking for mtree... /usr/sbin/mtree checking for cvs... /usr/bin/cvs checking for svn... /usr/bin/svn checking for rsync... /usr/bin/rsync checking for sed... /usr/bin/sed checking for tar... /usr/bin/tar checking for make... /usr/bin/make checking for launchd... no checking for launchctl... /bin/launchctl checking for xcodebuild... /usr/bin/xcodebuild checking for gnutar... /usr/bin/gnutar checking for gnumake... /usr/bin/gnumake checking for bzip2... /usr/bin/bzip2 checking for xar... /usr/bin/xar checking for open... /usr/bin/open checking for sed... (cached) /usr/bin/sed checking which sed flag to use for extended regexp... -E (BSD) checking for tar... (cached) /usr/bin/tar checking for gnutar... (cached) /usr/bin/gnutar checking for which tar variant to use... /usr/bin/gnutar checking for /usr/bin/gnutar --no-same-owner support... yes checking how to mark unused variables... checking for gcc symbol visibility attribute... __attribute__((visibility("hidden"))) checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... -D_THREAD_SAFE checking how to run the Objective C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... rm: conftest.dSYM: is a directory rm: conftest.dSYM: is a directory yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking objc/objc.h usability... yes checking objc/objc.h presence... yes checking for objc/objc.h... yes checking if linking libobjc requires pthreads... no checking for Apple Objective-C runtime... yes checking for GNU Objective C runtime... no configure: Using Apple Objective-C runtime checking for Apple Foundation library... yes configure: WARNING: GNUSTEP_SYSTEM_ROOT is not defined in your environment, preventing the use of GNUstep's Foundation library configure: Using Apple Foundation library checking for CoreFoundation framework... yes checking for SystemConfiguration framework... yes checking for IOKit framework... yes checking for CFNotificationCenterGetDarwinNotifyCenter... yes checking for whether we will build daemondo... yes checking for ports tree... configure: WARNING: No ports tree found checking for MacPorts config directory... ${sysconfdir}/macports checking for install user... mp-user checking for install group... mp-user checking what permissions to use for installation directories... 0755 checking how to run the C preprocessor... gcc -E checking for ANSI C header files... (cached) yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for sys/wait.h that is POSIX.1 compatible... yes checking whether stat file-mode macros are broken... no checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking paths.h usability... yes checking paths.h presence... yes checking for paths.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking crt_externs.h usability... yes checking crt_externs.h presence... yes checking for crt_externs.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking sys/fcntl.h usability... yes checking sys/fcntl.h presence... yes checking for sys/fcntl.h... yes checking sys/cdefs.h usability... yes checking sys/cdefs.h presence... yes checking for sys/cdefs.h... yes checking err.h usability... yes checking err.h presence... yes checking for err.h... yes checking libgen.h usability... yes checking libgen.h presence... yes checking for libgen.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking readline/readline.h usability... yes checking readline/readline.h presence... yes checking for readline/readline.h... yes checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking sys/paths.h usability... yes checking sys/paths.h presence... yes checking for sys/paths.h... yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking whether closedir returns void... no checking for pid_t... yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... no checking for bzero... yes checking for memset... yes checking for dup2... yes checking for regcomp... yes checking for strdup... yes checking for strerror... yes checking for strtol... yes checking for fgetln... yes checking for lockf... yes checking for flock... yes checking for setmode... yes checking for strcasecmp... yes checking for strncasecmp... yes checking for strlcpy... yes checking for copyfile... yes checking if readlink conforms to POSIX 1003.1a... yes checking for MD5Update in -lmd... no checking for MD5_Update in -lcrypto... yes checking openssl/md5.h usability... yes checking openssl/md5.h presence... yes checking for openssl/md5.h... yes checking for X... no checking for XOpenDisplay in -lX11... yes Please install the X11 SDK packages from the Xcode Developer Tools CD configure: error: Broken X11 install. No X11 headers ./configure script failed.

1 0