Date: Sat, 2 Feb 2002 17:09:20 +0100 From: F.Xavier Noria <fxn@retemail.es> To: freebsd-questions@freebsd.org Subject: Re: Problems with /usr/ports/Mk/bsd.port.mk (solved) Message-ID: <20020202170920.37310107.fxn@retemail.es> In-Reply-To: <20020202133940.1e7eabc5.fxn@retemail.es> References: <20020202133940.1e7eabc5.fxn@retemail.es>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Feb 2002 13:39:40 +0100
F. Xavier Noria <fxn@retemail.es> wrote:
: I have updated the ports tree and portsdb -uU gives lots of segmentation
: faults, I've tried to build some ports but make stops with errors. I am
: lost because AFAICT I have not touched /usr/ports/Mk/bsd.port.mk and
: have no clue about what could be happening, what do you think from this
: output of portsdb -uU (there are lots of lines like these)?
:
: Updating the ports index ...Segmentation fault - core dumped: malformed entry: Segmentation fault - core dumped
: Segmentation fault - core dumped: malformed entry: Segmentation fault - core dumped
: "/usr/ports/Mk/bsd.port.mk", line 609: warning: "/usr/bin/uname -r : malformed entry: "/usr/ports/Mk/bsd.port.mk", line 609: warning: "/usr/bin/uname -r | /usr/bin/sed -e 's/[-(].*//'" returned non-zero status
Just as a matter of feedback, the problem is solved, though I don't
understand why (which is a shame). In the very command line
# /usr/bin/uname -r | /usr/bin/sed -e 's/[-(].*//'
gave a nice sed.core. As I hadn't a clue about what to do, fsck /usr
reported nothing special, and this is my desktop at home, I decided to
reboot the machine. After that everythig is find again.
Hmmm....
-- fxn
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020202170920.37310107.fxn>