traceroute-1.4a12 / current / Darwin
Hello ! to compile traceroute on Darwin, I had to tweak 2 files with a very short change (aclocal.m4 and findsaddr-socket.c). Something more heavy was needed, replace original config.sub and config.guess by the one provided by Apple (last update, 1999 whereas traceroute has 1996). Change is about 2000 lines .. running aclocal ; autoconf ; configure ; make works like a charm after this... Are patches for Darwin accepted in current for openpkg ? If yes, what should I do about config.guess and config.sub ? Push patch for the moment, ask the upstream packager to update their version, and remove the patch when done ? diff -Naur traceroute-1.4a12/aclocal.m4 traceroute-1.4a12.patched/aclocal.m4 --- traceroute-1.4a12/aclocal.m41999-08-15 01:50:09 +0200 +++ traceroute-1.4a12.patched/aclocal.m42007-07-19 00:42:08 +0200 @@ -677,7 +677,7 @@ AC_TRY_LINK(dnl ifelse([$2], [main], , dnl Avoid conflicting decl of main. [/* Override any gcc2 internal prototype to avoid an error. */ -]ifelse(AC_LANG, CPLUSPLUS, [#ifdef __cplusplus +]ifelse(_AC_LANG_CURRENT, CPLUSPLUS, [#ifdef __cplusplus extern C #endif ])dnl (to fix configure.in:30: error: AC_LANG: unknown language: when running autoconf) diff -Naur traceroute-1.4a12/findsaddr-socket.c traceroute-1.4a12.patched/findsaddr-socket.c --- traceroute-1.4a12/findsaddr-socket.c2000-11-23 21:17:21 +0100 +++ traceroute-1.4a12.patched/findsaddr-socket.c2007-07-19 00:42:08 +0200 @@ -190,6 +190,7 @@ default: /* empty */ + ; } if (SALEN(sa) == 0) (to fix error: label at end of compound statement at line 193) Best Regards, Olivier Kaloudoff __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
Re: traceroute-1.4a12 / current / Darwin
Hi, I don't have a Mac available so here is some blind patch. You might try to pick up those files from the config package with following diff: diff -u -d -r1.23 traceroute.spec --- traceroute.spec 1 Jan 2007 17:42:26 - 1.23 +++ traceroute.spec 20 Jul 2007 12:26:09 - @@ -33,7 +33,7 @@ Group:Mapping License: BSD Version: 1.4a12 -Release: 20061013 +Release: 20070720 # list of sources Source0: ftp://ftp.ee.lbl.gov/traceroute-%{version}.tar.gz @@ -42,7 +42,7 @@ # build information Prefix: %{l_prefix} BuildRoot:%{l_buildroot} -BuildPreReq: OpenPKG, openpkg = 20040130 +BuildPreReq: OpenPKG, openpkg = 20040130, config PreReq: OpenPKG, openpkg = 20040130 AutoReq: no AutoReqProv: no @@ -65,6 +65,7 @@ %prep %setup -q %patch -p0 +%{l_prefix}/bin/config install %build CC=%{l_cc} \ -cs __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
Re: traceroute-1.4a12 / current / Darwin
On Thu, Jul 19, 2007, Olivier Kaloudoff wrote: to compile traceroute on Darwin, I had to tweak 2 files with a very short change (aclocal.m4 and findsaddr-socket.c). Something more heavy was needed, replace original config.sub and config.guess by the one provided by Apple (last update, 1999 whereas traceroute has 1996). Change is about 2000 lines .. For bringing the config.* files to a newer level you can just require the config package and then run %{l_prefix}/bin/config install . in the traceroute.spec:%build. This way you especially do not need the aclocal.m4 patch and no dependency to AutoXXX. running aclocal ; autoconf ; configure ; make works like a charm after this... Are patches for Darwin accepted in current for openpkg ? If yes, what should I do about config.guess and config.sub ? Push patch for the moment, ask the upstream packager to update their version, and remove the patch when done ? Sure, Darwin is just fine. Kick your findsaddr-socket.c fix and the the above config install into our traceroute package, please. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
[CVS] OpenPKG: ACCESS DENIED: Christoph Schug
ATTENTION: ACCESS DENIED OpenPKG CVS Repository denied COMMIT access for user Christoph Schug [EMAIL PROTECTED] on files: o openpkg-src/varnish/rc.varnish:HEAD o openpkg-src/varnish/varnish.patch:HEAD o openpkg-src/varnish/varnish.spec:HEAD __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
Re: [CVS] OpenPKG: ACCESS DENIED: Christoph Schug
On Fri, Jul 20, 2007, Christoph Schug wrote: ATTENTION: ACCESS DENIED OpenPKG CVS Repository denied COMMIT access for user Christoph Schug [EMAIL PROTECTED] on files: o openpkg-src/varnish/rc.varnish:HEAD o openpkg-src/varnish/varnish.patch:HEAD o openpkg-src/varnish/varnish.spec:HEAD Just don't panic, guys. Thomas is busy in performing a mass commit for about 100 packages and for this he just temporarily disabled all developer access. Once you see his commit mail you should be again able to commit just fine. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
Re: Milter build problems again.
On Fri, Jul 20, 2007, Mark Keller wrote: I had discussed a milter problem before in a previous request to the openpkg-dev list. http://marc.info/?l=openpkg-devm=117147128624622w=2 It turns out I have the problem again now that I am trying to uprade our packages. The mimedefang package fails to build because it is looking for the milter include files in libmilter/*.h, but openpkg seems to install the includes in milter/*.h. milter_cap.c:15:29: error: libmilter/mfapi.h: No such file or directory In file included from milter_cap.c:16: milter_cap.h:15:2: error: #error You must include libmilter/mfapi.h before milter_cap.h The fix that Ralph made last time at least got the package to build, but now that I look at the cvs log I don't see how that fixed the problem and it certainly doesn't work now. I do have binaries from last time, but can't repeat the process now. Yes, seems like mimedefang introduced another source file which needs patching now, too. Now fixed. Anyhow, I am wondering why the decision was made to move the milter include files to milter/*.h instead of the default libmilter/*.h? If something really needs the includes in milter/*.h maybe a symbolic link should be made so it works for both locations. Maybe I am just missing something, but any ideas would be helpful. Simply because a package named foo should provide its includes in prefix/include or prefix/include/foo and not in any other location. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org
Milter build problems again.
I had discussed a milter problem before in a previous request to the openpkg-dev list. http://marc.info/?l=openpkg-devm=117147128624622w=2 It turns out I have the problem again now that I am trying to uprade our packages. The mimedefang package fails to build because it is looking for the milter include files in libmilter/*.h, but openpkg seems to install the includes in milter/*.h. milter_cap.c:15:29: error: libmilter/mfapi.h: No such file or directory In file included from milter_cap.c:16: milter_cap.h:15:2: error: #error You must include libmilter/mfapi.h before milter_cap.h The fix that Ralph made last time at least got the package to build, but now that I look at the cvs log I don't see how that fixed the problem and it certainly doesn't work now. I do have binaries from last time, but can't repeat the process now. Anyhow, I am wondering why the decision was made to move the milter include files to milter/*.h instead of the default libmilter/*.h? If something really needs the includes in milter/*.h maybe a symbolic link should be made so it works for both locations. Maybe I am just missing something, but any ideas would be helpful. Thanks, Mark __ OpenPKG http://openpkg.org Developer Communication List openpkg-dev@openpkg.org