Re: is anyone working on a openjdk port
matt donovan schrieb: I been thinking about making it but if someone already started I won't I just not had the time at the moment to start it since it'll be good to have in the port tree even if it needs a java installed to bootstrap it There already is a java/openjdk6 port in the tree and there was some email traffic about openjdk7 . Greetings Uli. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
is anyone working on a openjdk port
I been thinking about making it but if someone already started I won't I just not had the time at the moment to start it since it'll be good to have in the port tree even if it needs a java installed to bootstrap it ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [PATCH] trafshow port broken
Rui Paulo wrote:
On 27 Mar 2009, at 23:56, Lawrence Stewart wrote:
Hi Alexey,
You're listed as the maintainer for the FreeBSD net/trafshow port. The
port doesn't compile on 8.0-CURRENT (r190457) amd64 at the moment. The
recent import of the new pcap into FreeBSD 8 means pcap.h no longer
includes the system's net/bpf.h, which has a required #define ioctl
(BIOCIMMEDIATE). Placing the attached patch in the port's files
directory fixes the issue for me. The patch should only be required
for ${OSVERSION} >= 800074.
Rui, is patching the port the correct fix for this issue?
I think so. Hard to tell without looking at the program itself.
Ok cool. Just wanted to check that this wasn't *unexpected* fallout from
the recent pcap import and that a conscious decision has been made to
not include the system's bpf.h in pcap.h. Probably worth keeping an eye
out on the ports build cluster for any other ports that look like
they're failing to build because of bpf.h issues.
Cheers,
Lawrence
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [PATCH] trafshow port broken
On 27 Mar 2009, at 23:56, Lawrence Stewart wrote:
Hi Alexey,
You're listed as the maintainer for the FreeBSD net/trafshow port.
The port doesn't compile on 8.0-CURRENT (r190457) amd64 at the
moment. The recent import of the new pcap into FreeBSD 8 means
pcap.h no longer includes the system's net/bpf.h, which has a
required #define ioctl (BIOCIMMEDIATE). Placing the attached patch
in the port's files directory fixes the issue for me. The patch
should only be required for ${OSVERSION} >= 800074.
Rui, is patching the port the correct fix for this issue?
I think so. Hard to tell without looking at the program itself.
--
Rui Paulo
PGP.sig
Description: This is a digitally signed message part
Free Image Hosting
BlizzardImageHosting.com is a new leader in online image & photo hosting, portfolios, and slideshow creation. We offer features you wont find at other image hosting sites and we offer it FOR FREE! - Upload Unlimited Images - Share Images With Anyone and Anywhere - Get Gigabytes of Monthly Bandwidth and much more... Sign up now! http://blizzardimagehosting.com/ (c) 2003-2009 Blizzard Image Hosting All Rights Reserved ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[PATCH] trafshow port broken
Hi Alexey,
You're listed as the maintainer for the FreeBSD net/trafshow port. The
port doesn't compile on 8.0-CURRENT (r190457) amd64 at the moment. The
recent import of the new pcap into FreeBSD 8 means pcap.h no longer
includes the system's net/bpf.h, which has a required #define ioctl
(BIOCIMMEDIATE). Placing the attached patch in the port's files
directory fixes the issue for me. The patch should only be required for
${OSVERSION} >= 800074.
Rui, is patching the port the correct fix for this issue?
Cheers,
Lawrence
--- show_dump.c.orig2009-03-28 10:33:29.0 +1100
+++ show_dump.c 2009-03-28 10:28:44.0 +1100
@@ -30,6 +30,7 @@
#include
#include
#include
+#include
#include
#include
#include
--- trafshow.c.orig 2009-03-28 10:33:50.0 +1100
+++ trafshow.c 2009-03-28 10:27:52.0 +1100
@@ -30,6 +30,7 @@
#include
#include
#include
+#include
#include
#include
#include
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of devel/boost upgrade
On Fri, 27 Mar 2009 09:29:19 -0600, Dmitry Marakasov wrote: * Alexander Churanov (alexanderchura...@gmail.com) wrote: As stated on http://wiki.freebsd.org/BoostPortingProject, all issues with ports depending on devel/boost are resolved. Thank guys for work on boost stuff. Should I do something for updating the port? We're planning extra exp-run with all the fixes and patch to boost, pav@ is going to start it on Sunday evening. The update itself is planned for 6th, as we're still awaiting approvals or timeouts for 2 PRs. For now all we need is to wait for exp-run results and fix extra bugs, if there are any. You do not need to wait for the PRs to either get approve or timeout if it is part of boost update. It's basicaully already approved by portmgr by tested in the exp-run. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/icu: doesn't build at 8-CURRENT
My build on a recent snapshot of 8-CURRENT succeeds without any problems. There are different failures reported here, but some of them appear to be related to the vfs problem found in PRs kern/132620 and ports/132542, and solved a series of changes ending in subversion r190145 on 20 Mar. 2009. Some of you should update your base systems and try again if you don't have these revisions. Regards, b. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/icu: doesn't build at 8-CURRENT
--- On Fri, 3/27/09, bf wrote: > From: bf > Subject: Re: devel/icu: doesn't build at 8-CURRENT > To: po...@freebsd.org > Cc: r...@freebsd.org, b...@ipt.ru, m...@aldan.algebra.com > Date: Friday, March 27, 2009, 6:17 PM > My build on a recent snapshot of > 8-CURRENT succeeds without any > problems. There are different failures reported here, > but some of > them appear to be related to the vfs problem found in PRs > kern/132620 and ports/132542, and solved a series of > changes > ending in subversion r190145 on 20 Mar. 2009. Some of > you should > update your base systems and try again if you don't have > these > revisions. > > Regards, > b. > > > > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
A couple of fixes fvwm95
Hi ports@ folks, I use fvwm95 and now that suspend/resume is working for amd64 I've switched over to 64bit. However, fvwm95's task bar doesn't show up when built for amd64. This patch seems to fix it: --- modules/FvwmTaskBar/Mallocs.c.orig Wed Mar 21 14:02:08 2007 +++ modules/FvwmTaskBar/Mallocs.c Wed Mar 21 14:02:25 2007 @@ -19,6 +19,7 @@ * as long as the copyright is kept intact. */ #include +#include #include #include #include and this patch seems to fix a -current compile problem: --- fvwm/misc.h.orig2009-03-27 09:02:02.0 -0700 +++ fvwm/misc.h 2009-03-27 09:02:19.0 -0700 @@ -320,7 +320,7 @@ void ButtonStyle(XEvent *eventp,Window w unsigned long context, char *action,int *Module); void SetColormapFocus(XEvent *eventp,Window w,FvwmWindow *tmp_win, unsigned long context, char *action,int* Module); -inline void DrawPattern(Window, GC, GC, int, int,int); +void DrawPattern(Window, GC, GC, int, int,int); PixelGetShadow(Pixel); PixelGetHilite(Pixel); Since ports@ is the maintainer I'd figure I'd bounce it off the ports email list. I used to be a ports committer (still src). Thanks, Doug A. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[Fwd: Re: devel/icu: doesn't build at 8-CURRENT]
forwarded to ports ml. I'm not working on it. Originele bericht Onderwerp: Re: devel/icu: doesn't build at 8-CURRENT Datum: Fri, 27 Mar 2009 16:50:12 +0100 Van: Diego Depaoli Aan: Rene Ladan Referenties: <93151...@serv3.int.kfs.ru> <49ccc7e8.5010...@gmail.com> <49ccdaea.7090...@aldan.algebra.com> <49ccf19f.6090...@freebsd.org> 2009/3/27 Rene Ladan : The port builds succesfully when commenting out the ALL_TARGET line. someone is working on icu 4? Cheers -- Diego Depaoli -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/icu: doesn't build at 8-CURRENT
Mikhail T. schreef: Rene Ladan написав(ла): Boris Samorodov schreef: [...] cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o wrtxml.o wrtxml.c c++ -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o prscmnts.o prscmnts.cpp cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o derb.o derb.c cd ../.. \ && CONFIG_FILES=tools/genrb/derb.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating tools/genrb/derb.1 cd ../.. \ && CONFIG_FILES=tools/genrb/genrb.1 CONFIG_HEADERS= /bin/sh ./config.status ./config.status: Can't open ./config.status: No such file or directory gmake[2]: *** [genrb.1] Error 2 Same on 7.1-RELEASE/amd64, the THREAD option is on. Ports tree is from 2009-03-27 09:57:43 UTC Does it help to comment out the ALL_TARGET line from the port's Makefile? Thanks, The port builds succesfully when commenting out the ALL_TARGET line. Rene ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of devel/boost upgrade
* Alexander Churanov (alexanderchura...@gmail.com) wrote: > As stated on http://wiki.freebsd.org/BoostPortingProject, all issues > with ports depending on devel/boost are resolved. > Should I do something for updating the port? We're planning extra exp-run with all the fixes and patch to boost, pav@ is going to start it on Sunday evening. The update itself is planned for 6th, as we're still awaiting approvals or timeouts for 2 PRs. For now all we need is to wait for exp-run results and fix extra bugs, if there are any. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Status of devel/boost upgrade
Hi folks! As stated on http://wiki.freebsd.org/BoostPortingProject, all issues with ports depending on devel/boost are resolved. Should I do something for updating the port? Sincerely, Alexander Churanov, maintainer of devel/boost ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/icu: doesn't build at 8-CURRENT
Rene Ladan написав(ла): Boris Samorodov schreef: [...] cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o wrtxml.o wrtxml.c c++ -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o prscmnts.o prscmnts.cpp cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o derb.o derb.c cd ../.. \ && CONFIG_FILES=tools/genrb/derb.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating tools/genrb/derb.1 cd ../.. \ && CONFIG_FILES=tools/genrb/genrb.1 CONFIG_HEADERS= /bin/sh ./config.status ./config.status: Can't open ./config.status: No such file or directory gmake[2]: *** [genrb.1] Error 2 Same on 7.1-RELEASE/amd64, the THREAD option is on. Ports tree is from 2009-03-27 09:57:43 UTC Does it help to comment out the ALL_TARGET line from the port's Makefile? Thanks, -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: qtiplot-0.9.7.5
On Fri, 27 Mar 2009 14:23:20 +1100, Mattia Rossi wrote: > Hi, > > as the qtiplot-0.9.7.2 port just didn't want to install python > scripting, I thought it's a qtiplot issue and tried to install qtiplot > 0.9.7.5. Well didn't work so well without all the patching, so I finally > got a working installation, by creating a new port. Don't get you problem. Do you build qtiplot with PYTHON option enabled? > I have no idea whether this was the correct way of patching qtiplot, as > I'm using the shipped 3rdparty qwt and qwt3dplot rather than system wide > installations (the shipped ones contain some slight adaptations for > qtiplot). The port works for me anyhow, I have qtiplot 0.9.7.5 and can > do Python scripting. > > Have no idea how to generate the package-plist so I used the old one. > > Have a look at the tarball, and maybe you can create a proper release soon. I've updated qwt and qtiplot locally, I'll commit them after some testing. You could try them as well: http://people.freebsd.org/~makc/patches/qwt520.patch http://people.freebsd.org/~makc/patches/qtiplot975.patch Update qwt first and then build qtiplot. I've enabled python support by default, it's considered as stable now. Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS UP multi processor compilations for everyone
* Pav Lucistnik (p...@freebsd.org) wrote:
> > second
> > also improves MAKE_JOBS_* handling, shortening it a bit and exposing
> > MAKE_JOBS_NUMBER to the ports, so it can be used for other build systems
> > without having to parse out -j from _MAKE_JOBS (and defaults to 1 if
> > jobs support is disabled).
>
> This one I cannot accept, because it adds back != call I made a big
> effort to avoid. We can't have one != call per port during building
> INDEX.
Understood. I still think it'd be nice to expose number of jobs as a
plain number to the ports.
> > Also, [ x != x${BUILD_FAIL_MESSAGE} ] thing seems to be a bit unsafe,
> > and inconsistent to IGNORE/BROKEN/... vars, in which we don't use
> > quotes.
>
> It's consistent with CONFIGURE_FAIL_MESSAGE. Why are you removing the
> parenthesis around the ${ECHO_CMD} ${BUILD_FAIL_MESSAGE}, BTW?
> Because they are present in do-configure target too - should they be
> removed there too?
I just didn't like them :) Are they really needed around single command?
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/icu: doesn't build at 8-CURRENT
Boris Samorodov schreef: Hi! the port devel/icu doesn't build at 8-CURRENT (I use tinderbox with 8-CURRENT built a couple of hours ago and the latest ports tree): - building icu-3.8.1_2 in directory /m/local/tinderbox/8-FreeBSD build started at Fri Mar 27 09:32:38 UTC 2009 port directory: /usr/ports/devel/icu building for: 8.0-CURRENT i386 maintained by: m...@aldan.algebra.com Makefile ident: $FreeBSD: ports/devel/icu/Makefile,v 1.31 2009/03/25 16:42:58 mi Exp $ [...] cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o wrtxml.o wrtxml.c c++ -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o prscmnts.o prscmnts.cpp cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o derb.o derb.c cd ../.. \ && CONFIG_FILES=tools/genrb/derb.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating tools/genrb/derb.1 cd ../.. \ && CONFIG_FILES=tools/genrb/genrb.1 CONFIG_HEADERS= /bin/sh ./config.status ./config.status: Can't open ./config.status: No such file or directory gmake[2]: *** [genrb.1] Error 2 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/tools/genrb' gmake[1]: *** [all-recursive] Error 2 gmake[1]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/tools' gmake: *** [all-recursive] Error 2 gmake -C /work/a/ports/devel/icu/work/icu/source/test gmake: Entering directory `/work/a/ports/devel/icu/work/icu/source/test' gmake[0]: Making `all' in `testdata' gmake[1]: Entering directory `/work/a/ports/devel/icu/work/icu/source/test/testdata' /bin/sh ../../mkinstalldirs ../../test/testdata/out ../../test/testdata/out/build ../../test/testdata/out/testdata mkdir ../../test/testdata/out mkdir ../../test/testdata/out/build mkdir ../../test/testdata/out/testdata gmake[1]: *** No rule to make target `../../tools/gentest/gentest', needed by `../../test/testdata/out/build/test.icu'. Stop. gmake[1]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/test/testdata' gmake: *** [all-recursive] Error 2 gmake: Leaving directory `/work/a/ports/devel/icu/work/icu/source/test' *** Error code 2 (ignored) cd /work/a/ports/devel/icu/work/icu/source/test/iotest && /usr/bin/env LD_LIBRARY_PATH=/work/a/ports/devel/icu/work/icu/source/lib:/work/a/ports/devel/icu/work/icu/source/tools/ctestfw ./iotest env: ./iotest: No such file or directory *** Error code 127 Stop in /a/ports/devel/icu. - Same on 7.1-RELEASE/amd64, the THREAD option is on. Ports tree is from 2009-03-27 09:57:43 UTC Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[PATCH] pilot-link port (as dependency of kdepim-4.2.1) broken by new usb
Hi,
You're listed as the maintainer for the FreeBSD palm/pilot-link port. It
gets pulled in as a dependency of libmal, which in turn is required by
kdepim-4.2.1. On FreeBSD 8-CURRENT, the new USB stack has broken the
build of this port. The attached patch allows the port to compile. The
patch is only required if ${OSVERSION} >= 800064.
I tested on 8.0-CURRENT (r190457) amd64.
Cheers,
Lawrence
--- libpisock/freebsdusb.c.orig 2006-10-13 00:21:22.0 +1000
+++ libpisock/freebsdusb.c 2009-03-27 22:37:32.0 +1100
@@ -48,7 +48,7 @@
#if defined(__FreeBSD__)
/* freebsd usb header */
-#include
+#include
#define MAX_BUF 256
#endif
@@ -98,7 +98,7 @@
i,
endpoint_fd;
- struct usb_device_info udi;
+ struct usb2_device_descriptor udi;
/* struct usb_ctl_request ur; */
/* unsigned char usbresponse[50]; */
@@ -173,18 +173,18 @@
will don't know exactly
what is coming so we can't specify exact byte amounts */
i = 1;
- if (ioctl(endpoint_fd, USB_SET_SHORT_XFER, &i) < 0) {
+ if (ioctl(endpoint_fd, USB_SET_RX_SHORT_XFER, &i) < 0) {
LOG((PI_DBG_DEV, PI_DBG_LVL_WARN,
-"DEV USB_SET_SHORT_XFER USB FreeBSD fd: %d failed\n",
+"DEV USB_SET_RX_SHORT_XFER USB FreeBSD fd: %d failed\n",
endpoint_fd));
}
/* 0 timeout value will cause us the wait until the device has data
available or is disconnected */
i = 0;
- if (ioctl(endpoint_fd, USB_SET_TIMEOUT, &i) < 0) {
+ if (ioctl(endpoint_fd, USB_SET_RX_TIMEOUT, &i) < 0) {
LOG((PI_DBG_DEV, PI_DBG_LVL_WARN,
-"DEV USB_SET_TIMEOUT USB FreeBSD fd: %d failed\n",
+"DEV USB_SET_RX_TIMEOUT USB FreeBSD fd: %d failed\n",
endpoint_fd));
}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/icu: doesn't build at 8-CURRENT
Hi! the port devel/icu doesn't build at 8-CURRENT (I use tinderbox with 8-CURRENT built a couple of hours ago and the latest ports tree): - building icu-3.8.1_2 in directory /m/local/tinderbox/8-FreeBSD build started at Fri Mar 27 09:32:38 UTC 2009 port directory: /usr/ports/devel/icu building for: 8.0-CURRENT i386 maintained by: m...@aldan.algebra.com Makefile ident: $FreeBSD: ports/devel/icu/Makefile,v 1.31 2009/03/25 16:42:58 mi Exp $ [...] cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o wrtxml.o wrtxml.c c++ -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o prscmnts.o prscmnts.cpp cc -I../../common -I../../i18n -I./../toolutil -pipe -O2 -fno-strict-aliasing -c -o derb.o derb.c cd ../.. \ && CONFIG_FILES=tools/genrb/derb.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating tools/genrb/derb.1 cd ../.. \ && CONFIG_FILES=tools/genrb/genrb.1 CONFIG_HEADERS= /bin/sh ./config.status ./config.status: Can't open ./config.status: No such file or directory gmake[2]: *** [genrb.1] Error 2 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/tools/genrb' gmake[1]: *** [all-recursive] Error 2 gmake[1]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/tools' gmake: *** [all-recursive] Error 2 gmake -C /work/a/ports/devel/icu/work/icu/source/test gmake: Entering directory `/work/a/ports/devel/icu/work/icu/source/test' gmake[0]: Making `all' in `testdata' gmake[1]: Entering directory `/work/a/ports/devel/icu/work/icu/source/test/testdata' /bin/sh ../../mkinstalldirs ../../test/testdata/out ../../test/testdata/out/build ../../test/testdata/out/testdata mkdir ../../test/testdata/out mkdir ../../test/testdata/out/build mkdir ../../test/testdata/out/testdata gmake[1]: *** No rule to make target `../../tools/gentest/gentest', needed by `../../test/testdata/out/build/test.icu'. Stop. gmake[1]: Leaving directory `/work/a/ports/devel/icu/work/icu/source/test/testdata' gmake: *** [all-recursive] Error 2 gmake: Leaving directory `/work/a/ports/devel/icu/work/icu/source/test' *** Error code 2 (ignored) cd /work/a/ports/devel/icu/work/icu/source/test/iotest && /usr/bin/env LD_LIBRARY_PATH=/work/a/ports/devel/icu/work/icu/source/lib:/work/a/ports/devel/icu/work/icu/source/tools/ctestfw ./iotest env: ./iotest: No such file or directory *** Error code 127 Stop in /a/ports/devel/icu. - Any help is appreciated. Thanks! WBR -- bsam ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS UP multi processor compilations for everyone
Dmitry Marakasov píše v pá 27. 03. 2009 v 04:02 +0300:
> * Pav Lucistnik (p...@freebsd.org) wrote:
>
> > > Btw, this change broke build failures. If vendor's make fails,
> > > .build_done.xxx._usr_local is still created in work and $? = 0 as if it
> > > have succeeded.
> >
> > Can you give me a hard example?
>
> Test port consisting of a sole Makefile attached.
>
> I've made two patches for bsd.port.mk.
> First one fixes this issue by adding some false's to do-build,
Ah right, I have stolen do-configure targets and missed the ${FALSE}.
Will fix.
> second
> also improves MAKE_JOBS_* handling, shortening it a bit and exposing
> MAKE_JOBS_NUMBER to the ports, so it can be used for other build systems
> without having to parse out -j from _MAKE_JOBS (and defaults to 1 if
> jobs support is disabled).
This one I cannot accept, because it adds back != call I made a big
effort to avoid. We can't have one != call per port during building
INDEX.
> Also, [ x != x${BUILD_FAIL_MESSAGE} ] thing seems to be a bit unsafe,
> and inconsistent to IGNORE/BROKEN/... vars, in which we don't use
> quotes.
It's consistent with CONFIGURE_FAIL_MESSAGE. Why are you removing the
parenthesis around the ${ECHO_CMD} ${BUILD_FAIL_MESSAGE}, BTW?
Because they are present in do-configure target too - should they be
removed there too?
--
Pav Lucistnik
Pain clots and unformed lice pat this train.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
