Re: Finding slowdowns in pkg_install (continuations of previous threads)

2007-07-05 Thread Garrett Cooper

Garrett Cooper wrote:
   I'm currently running a gamut of tests (500 tests, per package -- 
128 total on my server), and outputting all data to CSV files to 
interpret later, using another Perl script to interpret calculated 
averages and standard deviations.


   Using basic printf(2)'s with clock_gettime(2) I have determined 
that the majority of the issues are disk-bound (as Tom Kientzle put 
it). The scope of my problem is not to analyze tar, but I've 
discovered that a lot of time is spent in reading and interpreting the 
+CONTENTS and related files (most notably in parsing commands to be 
honest).


   Will post more conclusive results tomorrow once all of my results 
are available.


Cheers,
-Garrett

Forgot to include [EMAIL PROTECTED]
-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD Port: cfengine-2.2.1

2007-07-05 Thread Atmasamarpan

Hi,

Everything is fine after I removed db4-4.0.14_1,1. The port requires 
db44, but during configure it finds db4 and compilation fails. See bellow.


Thanks,
Atmasamarpan

===>  Patching for cfengine-2.2.1
===>  Applying FreeBSD patches for cfengine-2.2.1
===>   cfengine-2.2.1 depends on shared library: db-4.4.0 - found
===>  Configuring for cfengine-2.2.1

checking for BerkeleyDB location in default... Found header in 
/usr/local/include/db4

checking for library containing db_create... -ldb4
/usr/local
checking Berkeley DB Version... 4.0.14 OK
checking Berkeley DB API... 4.0.14 checking for db_create in -ldb... no
...
if cc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/include/db4 
-I/usr/include   -D_THREAD_SAFE -g -O2 -Wreturn-type 
-Wmissing-prototypes -Wuninitialized -D_THREAD_SAFE  -O -pipe  
-I/usr/local/include/db4  -D_THREAD_SAFE -DBUILDTIN_GCC_THREAD 
-D_THREAD_SAFE  -O -pipe  -I/usr/local/include/db4  -D_THREAD_SAFE 
-DBUILDTIN_GCC_THREAD -MT instrument.o -MD -MP -MF 
".deps/instrument.Tpo" -c -o instrument.o instrument.c;  then mv -f 
".deps/instrument.Tpo" ".deps/instrument.Po"; else rm -f 
".deps/instrument.Tpo"; exit 1; fi

instrument.c: In function `RecordPerformance':
instrument.c:65: error: incompatible type for argument 4 of indirect 
function call

instrument.c:65: error: too many arguments to function
*** Error code 1



Lowell Gilbert wrote:

Atmasamarpan <[EMAIL PROTECTED]> writes:

  

I am not able to compile cfengine both under 6.0 and 6.2. Am I doing
anything wrong?



Probably.  It builds fine for me with the latest ports under a fairly
recent -STABLE.  Can you give more information about you installation,
ports tree, etc.?
  

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[Fwd: Totem Compilation error.]

2007-07-05 Thread Vincent Blondel

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
[EMAIL PROTECTED], 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
([EMAIL PROTECTED]), 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.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [Fwd: freehdl-0.0.4_1 failed on i386 7]

2007-07-05 Thread [LoN]Kamikaze
Pav Lucistnik wrote:
> [LoN]Kamikaze píše v út 03. 07. 2007 v 16:04 +0200:
>> [LoN]Kamikaze wrote:
>>> Pav Lucistnik wrote:
  Přeposlaná zpráva 
> Od: User Ports-i386 <[EMAIL PROTECTED]>
> Komu: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> Předmět: freehdl-0.0.4_1 failed on i386 7
> Datum: Tue, 3 Jul 2007 02:20:29 GMT
>
> ...
>
> c++ -DPACKAGE_NAME=\"freehdl\" -DPACKAGE_TARNAME=\"freehdl\"
> -DPACKAGE_VERSION=\"0.0.4\" "-DPACKAGE_STRING=\"freehdl 0.0.4\""
> -DPACKAGE_BUGREPORT=\"[EMAIL PROTECTED]" -DSTDC_HEADERS=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DYYTEXT_POINTER=1 -DHAVE_FLEXLEXER_H=1
> -DHAVE_GETOPT_H=1 -DSIZEOF_INT=4 -DHAVE_VASPRINTF=1 -DHAVE_ALLOCA=1
> -DHAVE_SOCKET=1 -I. -I. -I .. -I .. -O2 -fno-strict-aliasing -pipe -MT
> vital_timing.lo -MD -MP -MF .deps/vital_timing.Tpo -c vital_timing.cc -o
> vital_timing.o >/dev/null 2>&1
> gmake[2]: *** [vital_timing.lo] Error 1
> gmake[2]: Leaving directory 
> `/work/a/ports/cad/freehdl/work/freehdl-0.0.4/ieee'
> gmake[1]: *** [all] Error 2
> gmake[1]: Leaving directory 
> `/work/a/ports/cad/freehdl/work/freehdl-0.0.4/ieee'
> gmake: *** [all-recursive] Error 1
> *** Error code 2
>
> Stop in /a/ports/cad/freehdl.
> 
> build of /usr/ports/cad/freehdl ended at Tue Jul  3 02:20:39 UTC 2007
>>> I was able to reproduce this on 6-Stable using gcc42 from ports and I will
>>> report this to the appropriate freehdl developers. Thank you for informing 
>>> me.
>>
>> I have to revoke that statement. Neither the mailing list, nor the emails
>> listed in AUTHORS are reachable. It's as if the project was silently 
>> abandoned.
>>
>> As a workaround, please try to add USE_GCC=3.4 to cad/freehdl/Makefile and 
>> tell
>> me weather it works.
> 
> I'm afraid you're supposed to tell me if adding USE_GCC works :)
> I'd much prefer fixing the port to compile with gcc42 than forcing old
> GCC on users - GCC is 40MB download. It's probably something trivial,
> anyway. Removing >/dev/null from the Makefiles will be a good first step
> to figure it out.
> 

If only I found these >/dev/null . But autotools and GNU Make are a mystery to
me. Also I don't see why someone would hide error messages on purpose.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [Fwd: Totem Compilation error.]

2007-07-05 Thread Michael Johnson

On 7/5/07, Vincent Blondel <[EMAIL PROTECTED]> 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
[EMAIL PROTECTED], 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
([EMAIL PROTECTED]), 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.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [Fwd: Totem Compilation error.]

2007-07-05 Thread Vincent Blondel
On Thu, July 5, 2007 13:42, Michael Johnson wrote:
On 7/5/07, Vincent Blondel <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED], 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
> ([EMAIL PROTECTED]), 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

I already compile my system with -O2 -pipe ...

portupgrade -f gstreamer-*

and you will be good to go.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My First Port

2007-07-05 Thread Wesley Shields
On Wed, Jul 04, 2007 at 12:53:45PM -0500, Paul Schmehl wrote:
>  --On July 4, 2007 4:49:33 PM +0200 Lars Engels <[EMAIL PROTECTED]> wrote:
> 
> > On Wed, Jul 04, 2007 at 09:28:45AM -0400, Michael W. Lucas wrote:
> >> On Tue, Jul 03, 2007 at 04:53:46PM -0500, Paul Schmehl wrote:
> >> >  good comments deleted
> >>
> >> Thanks, Shaun and Paul.  I appreciate the help.  Changes made,
> >> portlint ran, port re-tested, PR submitted.
> >>
> >> Somebody stop me before I port again!  :-)
> >
> > No, Sir!
> >
> > Porting is fun, so we won't stop you from having fun.
> > And if you're stuck with a more complicated port, just ask
> > for help. There are a lot of helpful maintainers and committers
> > around.  :)
> >
>  Speaking of difficult ports.
> 
>  I'm working on the upgrade to security/bro.  It's a royal PITA.  The author 
>  hardcodes destinations for everything so that the software doesn't follow 
>  FreeBSD conventions at all, *and* there's no "master" setting that you can 
>  alter in configure or the top level Makefile.in file.  So, I've had to edit 
>  almost every Makefile.in in the distro to get the darn thing to behave.  
>  Even the docs don't want to install where they should!
> 
>  Here's my FILESDIR:
> 
>  ls files/
>  patch-Makefile.in patch-policy-Makefile.in
>  patch-aux-scripts-Makefile.in patch-policy-sigs-Makefile.in
>  patch-configure patch-scripts-Makefile.in
>  patch-doc-quick-start-Makefile.in patch-scripts-s2b-bro-include-Makefile.in
>  patch-doc-ref-manual-Makefile.in 
>  patch-scripts-s2b-example-bro-files--Makefile.in
>  patch-doc-user-manual-Makefile.in patch-src-Makefile.in
> 
>  {{{sigh}}}
> 
>  I have one last problem.  This software installs another piece of software 
>  named "broccoli" (don't ask), and for some reason broccoli puts it's lib 
>  files in PREFIX/share.  I can't seem to find why it's doing that.  I grepped 
>  for libdir and it always appears as EPREFIX/lib, which is correct. If anyone 
>  wants to take a look at this thing and figure it out, I would be grateful.  
>  It's the one last piece I need to get this thing working as expected.
> 
>  You can download the source here: 

Paul,

As I mentioned before, I took a stab at this port a while ago and came
to the same conclusions.  I'll gladly take a look at where you are and
see if I can help you out at all.  Can you send a patch of where you
currently are so I can take a look?

-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Portupgrade lynx2.-8-6 compile failure

2007-07-05 Thread David Southwell
Currently installed version
**
pkg_info |grep lynx
lynx-2.8.6_5,1  A non-graphical, text-based World-Wide Web client

System
*
uname -a
FreeBSD dns1.vizion2000.net 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May  7 
04:15:57 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP  
amd64

Compile failure

 -DHAVE_CONFIG_H   -DLOCALEDIR=\"/usr/local/share/locale\"  -I.  -I..  
-Ichrtrans  -I./chrtrans  -I..  -I../src  -I../WWW/Library/Implementation
-O2 -fno-strict-aliasing -pipe -c ./LYList.c
cc  -I/usr/include -I/usr/include/ncurses  -I/usr/local/include -D_BSD_TYPES 
-D__BSD_VISIBLE -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DHAVE_CONFIG_H   
-DLOCALEDIR=\"/usr/local/share/locale\"  -I.  -I..  -Ichrtrans  -I./chrtrans  
-I..  -I../src  -I../WWW/Library/Implementation-O2 -fno-strict-aliasing 
-pipe -c ./LYCgi.c
cc  -I/usr/include -I/usr/include/ncurses  -I/usr/local/include -D_BSD_TYPES 
-D__BSD_VISIBLE -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DHAVE_CONFIG_H   
-DLOCALEDIR=\"/usr/local/share/locale\"  -I.  -I..  -Ichrtrans  -I./chrtrans  
-I..  -I../src  -I../WWW/Library/Implementation-O2 -fno-strict-aliasing 
-pipe -c ./LYTraversal.c
cc  -I/usr/include -I/usr/include/ncurses  -I/usr/local/include -D_BSD_TYPES 
-D__BSD_VISIBLE -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DHAVE_CONFIG_H   
-DLOCALEDIR=\"/usr/local/share/locale\"  -I.  -I..  -Ichrtrans  -I./chrtrans  
-I..  -I../src  -I../WWW/Library/Implementation-O2 -fno-strict-aliasing 
-pipe -c ./LYEditmap.c
cc  -I/usr/include -I/usr/include/ncurses  -I/usr/local/include -D_BSD_TYPES 
-D__BSD_VISIBLE -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DHAVE_CONFIG_H   
-DLOCALEDIR=\"/usr/local/share/locale\"  -I.  -I..  -Ichrtrans  -I./chrtrans  
-I..  -I../src  -I../WWW/Library/Implementation-O2 -fno-strict-aliasing 
-pipe -c ./LYCharSets.c
./LYCharSets.c: In function `HTMLGetEntityUCValue':
./LYCharSets.c:878: error: `unicode_entities' undeclared (first use in this 
function)
./LYCharSets.c:878: error: (Each undeclared identifier is reported only once
./LYCharSets.c:878: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/www/lynx/work/lynx2-8-6/src.
*** Error code 1

Stop in /usr/ports/www/lynx/work/lynx2-8-6.
*** Error code 1

Stop in /usr/ports/www/lynx.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.72731.31 
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=lynx-2.8.6_5,1 
UPGRADE_PORT_VER=2.8.6_5,1 make
** Fix the problem and try again.

Any ideas??


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD Port: cfengine-2.2.1

2007-07-05 Thread Scot Hetzel

On 7/5/07, Atmasamarpan <[EMAIL PROTECTED]> wrote:

Hi,

Everything is fine after I removed db4-4.0.14_1,1. The port requires 
db44, but during configure it finds db4 and compilation fails. See bellow.



I had a look at the ports Makefile, and found a couple of problems:.

USE_BDB?= 44

It should just be "=" instead of "?=" as the user overrides the default when 
using WITH_BDB_VER.  Since the port can only use BDB 4.4+, it should be specified as 44+.

Another problem, is that setting BERKELEY_DB_{CFLAGS, LDFLAGS, LIB} in the 
CONFIGURE_ENV has no effect, as the cfengine configure script is overriding 
these settings when it tries to detect the version of Berkeley DB that is 
installed.

checking for BerkeleyDB location in default... Found header in 
/usr/local/include/db4
checking for library containing db_create... -ldb4
/usr/local
BERKELEY_DB_LIB=-ldb4
BERKELEY_DB_CFLAGS=-I/usr/local/include/db4
BERKELEY_DB_LDFLAGS=-L/usr/local/lib
checking Berkeley DB Version... 4.0.14 OK
checking Berkeley DB API... 4.0.14 checking for db_create in -ldb... no

Note: I added a couple of echo statements before the version check.

I have submitted a PR 114333 with a fix for these problems.

http://www.freebsd.org/cgi/query-pr.cgi?pr=114333

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ChartDirector

2007-07-05 Thread Scot Hetzel

On 7/3/07, Mark Linimon <[EMAIL PROTECTED]> wrote:

On Mon, Jul 02, 2007 at 12:34:20PM +0200, Tim Rijavec wrote:
> can you add this package for ChartDirector for php to FreeBSD ports?
> that can be found at http://www.freebsd.org/ports/master-index.html

Please use send-pr to submit this so that it won't just get lost in the
mailing list traffic.  See:


PR 114336 contains the final port for php*-chartdirector
http://www.freebsd.org/cgi/query-pr.cgi?pr=114336

Note: there are also versions of chartdirector for ruby, perl, C++,
java that could be ported.

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [Fwd: Totem Compilation error.]

2007-07-05 Thread Vincent Blondel
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 <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED], 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
>> ([EMAIL PROTECTED]), 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



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Xorg related port upgrade questions

2007-07-05 Thread Dejan Lesjak


On Jul 3, 2007, at 9:41 PM, Jeffrey Williams wrote:


Ok,

I have a few of 6.2 servers (including two running in jails) that  
do not have full X installed, but they do have a number packages  
that depended on the various X libraries, fonts, and clients; and  
so these components of X are installed.


I have read through UPDATING and the mailing list, and it appears  
that the process as described that allows the use of portupgrade  
requires a full install of X.


My question is, can I still use portupgrade, with the manual  
upgrade of the libXft port, or should I manually deinstall and  
reinstall all the Xorg related ports, and the ports that depend on  
them.  If I go the manual reinstall route are their any make.conf  
values that need to be set to indicate I want the new file  
structure used, or have all the ports that used the "/usr/X11R6"  
directory been updated?


Even if you would need to install entire x11/xorg metaport, you can  
do that at the end of upgrade. If after upgrade you don't find  
anything missing then it shouldn't be necessary, but it's rather  
difficult to say in general. Not having the metaport installed will  
mostly affect users of xorg-server because of missing fonts and  
drivers that have been split up; users that have parts of X11 only as  
dependencies for some graphics tools less so.


Dejan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Portupgrade lynx2.-8-6 compile failure

2007-07-05 Thread Jan Henrik Sylvester

David Southwell wrote:
>Compile failure

>./LYCharSets.c: In function `HTMLGetEntityUCValue':
>./LYCharSets.c:878: error: `unicode_entities' undeclared (first use in 
>this function)


>Stop in /usr/ports/www/lynx/work/lynx2-8-6/src.

I had this problem, too.

Though, I have the latest ports tree (via portsnap), I am missing 
patch-LYCharSets (from 12 hours ago). With that, the port builds and 
installs fine.


My Makefile is not the latest, either.

Maybe it is because the last update of the port did not change the 
PORTREVISION (or PORTVERSION)? That should not interfere with portsnap 
updating the port, or should it? Or does portsnap have a "hiccup"?


Rather clueless
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Portupgrade lynx2.-8-6 compile failure

2007-07-05 Thread Jeffrey Goldberg

On Jul 5, 2007, at 7:52 PM, Jan Henrik Sylvester wrote:


David Southwell wrote:
>Compile failure

>./LYCharSets.c: In function `HTMLGetEntityUCValue':
>./LYCharSets.c:878: error: `unicode_entities' undeclared (first  
use in >this function)


>Stop in /usr/ports/www/lynx/work/lynx2-8-6/src.

I had this problem, too.

Though, I have the latest ports tree (via portsnap), I am missing  
patch-LYCharSets (from 12 hours ago). With that, the port builds  
and installs fine.


That would explain it.  I was able to get lynx to compile by patching  
LYCharSets.c


Details are with the PR that David filed.

  http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/114334


My Makefile is not the latest, either.

Maybe it is because the last update of the port did not change the  
PORTREVISION (or PORTVERSION)? That should not interfere with  
portsnap updating the port, or should it? Or does portsnap have a  
"hiccup"?


Your guess is as good as mine.

-j



--
Jeffrey Goldberghttp://www.goldmark.org/jeff/



Re: experimental qemu-devel port update, please test!

2007-07-05 Thread Eric Anderson

On 07/02/07 15:30, Juergen Lock wrote:

Looks like its time for this again...  Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc.  As always,
please test now, before I commit this, so we won't be in for
nasty surprises afterwards...


Works great so far on -CURRENT, thanks!

Did the vmwarevga thing ever settle down, and become stable?

Eric

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: experimental qemu-devel port update, please test!

2007-07-05 Thread Wilkinson, Alex
0n Thu, Jul 05, 2007 at 10:31:29PM -0500, Eric Anderson wrote: 

>On 07/02/07 15:30, Juergen Lock wrote:
>> Looks like its time for this again...  Many bugs have been fixed,
>> some features have been added, like, qemu-system-arm has grown
>> emulation of a few PDAs like some Zaurus models, etc.  As always,
>> please test now, before I commit this, so we won't be in for
>> nasty surprises afterwards...
>
>Works great so far on -CURRENT, thanks!
>Did the vmwarevga thing ever settle down, and become stable?
 
Whats the "vmwarevga thing" ?

 -aW

IMPORTANT: This email remains the property of the Australian Defence 
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 
1914.  If you have received this email in error, you are requested to contact 
the sender and delete the email.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"