Date: Sun, 14 Oct 2007 00:33:37 +0200 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: Luchezar Petkov <luchezar.petkov@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Weird problem with ports Message-ID: <471147C1.3000001@gmx.de> In-Reply-To: <47111003.2000908@gmail.com> References: <4710DD5A.7050303@gmail.com> <47112DFF.6040608@gmx.de> <47111003.2000908@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Luchezar Petkov wrote: > [LoN]Kamikaze wrote: >> Luchezar Petkov wrote: >>> Hello, >>> First, let me note that I'm not subscribed to this list, so CC me. >>> Now, about my problem. I've installed -CURRENT from the latest snapshot, >>> it worked perfectly. Now, after 2 days with -CURRENT, for some reason >>> all ports refuse to install, giving me weird errors. Example: >>> (Inkscape is not installed, hence the src tarball is not in distfiles, etc.) >>> >>> lilly# cd /usr/ports/graphics/inkscape/ >>> lilly# make install clean >>> cd: can't cd to /usr/ports/graphics/inkscape/work/inkscape-0.45.1 >>> *** Error code 2 >>> ===> Cleaning for inkscape-0.45.1 >>> 1 error >> make -j >> >> is broken on the 7-branch. Do you have something like MAKE_ARGS=-j4 in your >> make.conf? Weather this is the case or not, try to run >> >> make -B >> > > Apparently that was the case. Afaik -j isnt working for ports, but is > working for base and other apps the user is compiling by hand. Didn't > knew it will break my whole ports system. :-) > Thank you very much. > It breaks buildkernel for me, too. This is why I think it's not a ports, but a make bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?471147C1.3000001>