From owner-freebsd-gnome@FreeBSD.ORG Thu Jul 5 17:35:51 2007 Return-Path: X-Original-To: freebsd-gnome@freebsd.org Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7369F16A421 for ; Thu, 5 Jul 2007 17:35:51 +0000 (UTC) (envelope-from vincent@xtra-net.org) Received: from ns1.xtra-net.be (ns1.xtra-net.be [195.162.200.90]) by mx1.freebsd.org (Postfix) with SMTP id BD75F13C44C for ; Thu, 5 Jul 2007 17:35:50 +0000 (UTC) (envelope-from vincent@xtra-net.org) Received: (qmail 10151 invoked from network); 5 Jul 2007 17:35:49 -0000 Received: from unknown (HELO vbepfkad.srv.xtra-net.be) (172.16.66.70) by 0 with SMTP; 5 Jul 2007 17:35:49 -0000 Received: (qmail 80921 invoked from network); 5 Jul 2007 17:27:35 -0000 Received: from 72.66.16.172.in-addr.arpa (HELO www.xtra-net.be) (172.16.66.72) by 0 with SMTP; 5 Jul 2007 17:27:35 -0000 Received: from 172.16.9.1 (proxying for 192.168.1.10) (SquirrelMail authenticated user 720616030) by www.xtra-net.be with HTTP; Thu, 5 Jul 2007 19:27:35 +0200 (CEST) Message-ID: <37915.172.16.9.1.1183656455.squirrel@www.xtra-net.be> In-Reply-To: <5F6D65E8-5481-4DD7-8854-242E2A3236ED@ahze.net> References: <26493.172.16.9.1.1183623693.squirrel@www.xtra-net.be> <5F6D65E8-5481-4DD7-8854-242E2A3236ED@ahze.net> Date: Thu, 5 Jul 2007 19:27:35 +0200 (CEST) From: "Vincent Blondel" To: "Michael Johnson" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-ports@freebsd.org, freebsd-gnome@freebsd.org Subject: Re: [Fwd: Totem Compilation error.] X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 17:35:51 -0000 On Thu, July 5, 2007 14:03, Michael Johnson wrote: On Jul 5, 2007, at 7:42 AM, Michael Johnson wrote: > On 7/5/07, Vincent Blondel wrote: > >> >> Hello, >> >> >> I found a message somebody posted one year ago on your mailing >> list. I also get the same problem by trying to compile gnome CURRENT on >> my FreeBSD-CURRENT system. >> >> >> Can somebody say me if this problem is known and how I can solve it >> because I cannot go further with gnome compilation. >> >> Thanks >> Vincent. >> >> >> >> Hello, >> >> >> Below what I receive when trying to compile gnome2 CURRENT. This >> happens during the compilation phase of totem. >> >> checking whether to enable easy codec installation support... auto >> checking for MISSING_PLUGINS... yes checking for GST... yes checking for >> backend libraries... GStreamer-0.10 checking GStreamer 0.10 playbin >> plugin... no configure: error: >> Cannot find required GStreamer-0.10 plugin 'playbin'. >> It should be part of gst-plugins-base. Please install it. >> >> >> ===> Script configure failed unexpectedly. >> Please run the gnomelogalyzer, available from >> http://www.freebsd.org/gnome/gnomelogalyzer.sh, which will >> diagnose the problem and suggest a solution. If - and only if - the >> gnomelogalyzer cannot solve the problem, report the build failure to the >> FreeBSD GNOME >> team at gnome@FreeBSD.org, and attach (a) >> /tmp/usr/ports/multimedia/totem/work/totem-2.18.2/config.log, (b) >> the output of the failed make command, and (c) the gnomelogalyzer output. >> Also, it might >> be a good idea to provide an overview of all packages installed on your >> system (`ls -la`). Put your attachment up on any website, copy-and-paste >> into http://freebsd-gnome.pastebin.com, or use send- pr(1) with the >> attachment. Try to avoid sending any attachments to the mailing list >> (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing >> lists are usually discarded by the mailing list software. *** Error code 1 >> >> >> Stop in /usr/ports/multimedia/totem. >> >> >> If I look a bit more in detail it seems /usr/local/bin/gst-inspect is >> called during the configure phase and this causes segmentation fault. >> >> I already looked at google for some solution but without any success. >> >> >> Thanks to help me. >> Vincent. >> > > There is a long known problem that CFLAGS=-O1 or lower causes runtime > problems with gstreamer, and right now -CURRENT's default CFLAGS are -O1 > -pipe. > > > I added -O2 to gstreamer's CFLAGS in ports, so please run > > > portupgrade -f gstreamer-* > > and you will be good to go. ps Make sure you update your ports first though! I just finished recompiling all gstreamer-* ports and I always get the same result. You can look at the log files at http://jlang.dyndns.org/gstreamer.log Michael