Date: Wed, 05 Jun 2013 08:48:10 -0400 From: Nikolai Lifanov <lifanov@mail.lifanov.com> To: mdf@freebsd.org Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Cannot build ports on fresh 10.0 Message-ID: <51AF338A.6030002@mail.lifanov.com> In-Reply-To: <CALCpEUE-ZGBru6Z-Dc64_rv2T96RV94E7pUDo3Gpd6kFeTP4AQ@mail.gmail.com> References: <CAMBSHm-gcpk990WOjpr4Pn3Y=UZV4KOhH7XTqOKaD7pmP4gZmg@mail.gmail.com> <CALCpEUE-ZGBru6Z-Dc64_rv2T96RV94E7pUDo3Gpd6kFeTP4AQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/04/13 18:07, hiren panchasara wrote: > On Tue, Jun 4, 2013 at 2:42 PM, <mdf@freebsd.org> wrote: >> I installed a new VM with 10.0 today from this .iso: >> >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/amd64/10.0/FreeBSD-10.0-CURRENT-amd64-20130601-r251213-release.iso >> >> And I'm behind a firewall and I'm not sure I can use pkg(1); my one attempt >> failed: >> >> # pkg install m4 >> Updating repository catalogue >> Repository catalogue is up-to-date, no need to fetch fresh copy >> pkg: Package 'm4' was not found in the repositories >> >> So I'm building from source. But the configure step of various ports fails >> like so: >> >> checking whether make sets $(MAKE)... yes >> checking build system type... Invalid configuration >> `amd64-portbld-freebsd10.0': machine `amd64-portbld' not recognized >> configure: error: /bin/sh libltdl/config/config.sub >> amd64-portbld-freebsd10.0 failed >> ===> Script "configure" failed unexpectedly. >> Please report the problem to autotools@FreeBSD.org [maintainer] and attach >> the "/usr/ports/devel/libtool/work/libtool-2.4.2/config.log" including the >> output of the failure of your make command. Also, it might be a good idea to >> provide an overview of all packages installed on your system (e.g. a >> /usr/local/sbin/pkg-static info -g -Ea). >> *** Error code 1 > > _Probably_ similar to this? > http://lists.freebsd.org/pipermail/freebsd-ports/2013-June/084040.html > > cheers, > Hiren >> >> Any ideas what could be wrong? It's a fresh install with default options, >> so it seems hard to believe I managed to screw something up already. >> Posting on -current since this happens to many of the ports when I try to >> build them. >> >> Thanks, >> matthew >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > What you see has been fixed in ports r319875. You can sync your tree to past that and try again. Also, you can try the same proxy settings from libfetch. - Nikolai Lifanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51AF338A.6030002>