Date: Sat, 17 Sep 2005 14:19:27 -0700 From: Colin Percival <cperciva@freebsd.org> To: pergesu@gmail.com Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: portsnap segmentation fault Message-ID: <432C885F.7030400@freebsd.org> In-Reply-To: <810a540e05091713564a810a4a@mail.gmail.com> References: <810a540e05091713564a810a4a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pat Maddox wrote: > When I run portsnap update, I get the following error after it > extracts the files: > Building new INDEX files... Segmentation fault (core dumped) > > Any ideas what's going on? There is a bug in versions of portsnap prior to today which causes make_index to core dump when it encounters a cyclic dependency. To make portsnap work properly again, you can either 1. Upgrade your base system to the latest HEAD or RELENG_6 (if you are using portsnap from the base system), 2. Upgrade to the latest version of portsnap (0.9.5) in the ports tree, or 3. Wait until somebody fixes the audio/timidity++ port. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?432C885F.7030400>