building wine in jail fails

2008-03-23 Thread Dominic Fandrey
I'm trying to build wine in an i386 jail on amd64. All dependencies built just 
fine, only wine itself complains:


cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_ADVAPI32_ 
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing 
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith 
-I/usr/local/include -O2 -fno-strict-aliasing -pipe -march=prescott  -o 
service.o service.c
LD_LIBRARY_PATH="../../libs/wine:$LD_LIBRARY_PATH" ../../tools/wrc/wrc 
--nostdinc -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_ADVAPI32_ 
 -foversion.res version.rc

/libexec/ld-elf.so.1: Shared object "libwine.so.1" not found, required by "wrc"
gmake[2]: *** [version.res] Error 1
gmake[2]: Leaving directory 
`/usr/obj/usr/ports/emulators/wine/work/wine-0.9.57/dlls/advapi32'

gmake[1]: *** [advapi32] Error 2
gmake[1]: Leaving directory 
`/usr/obj/usr/ports/emulators/wine/work/wine-0.9.57/dlls'

gmake: *** [dlls] Error 2
*** Error code 2

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


portmaster and restarting of upgraded daemons

2008-03-23 Thread Miroslav Lachman
I am almost new to portmaster, so I got a question - is there any 
possibility to restart installed services as in portupgrade with defined 
BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future 
plan to do so? It is annoying if I end up with some dead services after 
upgrade just because I forgot to manualy do 
/usr/local/etc/rc.d/some_daemon restart


Next question - is there any documentation for portmaster.rc / 
.portmasterrc? I can't find any documentation for it on the internet, 
just some notices to search in portmaster script (source file) for 
"while getopts", where variables are defined, but it is not usual way to 
get documentation ;)


And last question - /etc/portmaster.rc - is it realy right place 
according to man hier? I would expect it in /usr/local/etc/portmaster.rc.


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


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Jeremy Chadwick
On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:
> I am almost new to portmaster, so I got a question - is there any 
> possibility to restart installed services as in portupgrade with defined 
> BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future plan 
> to do so? It is annoying if I end up with some dead services after upgrade 
> just because I forgot to manualy do /usr/local/etc/rc.d/some_daemon restart

This is more a complaint about the existing ports infrastructure, as
IMHO, it's something that should be handled there and not necessarily by
"third-party" port management utilities.

Some existing ports (such as smartmontools, i.e. smartd) do this, while
others (such as postfix) do not.

There are pros and cons to what you want.  I myself have never managed
to conclude if the pros outweigh the cons -- or vice-versa -- but I have
thought about it before.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Wesley Shields
On Sun, Mar 23, 2008 at 07:48:23AM -0700, Jeremy Chadwick wrote:
> On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:
> > I am almost new to portmaster, so I got a question - is there any 
> > possibility to restart installed services as in portupgrade with defined 
> > BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future plan 
> > to do so? It is annoying if I end up with some dead services after upgrade 
> > just because I forgot to manualy do /usr/local/etc/rc.d/some_daemon restart
> 
> This is more a complaint about the existing ports infrastructure, as
> IMHO, it's something that should be handled there and not necessarily by
> "third-party" port management utilities.
> 
> Some existing ports (such as smartmontools, i.e. smartd) do this, while
> others (such as postfix) do not.

There is an @stopdaemon facility which can be used in the plist.  In
fact, it might be a smart idea to remove the way smartmontools does it
and replace it with @stopdaemon for consistency sake.

> There are pros and cons to what you want.  I myself have never managed
> to conclude if the pros outweigh the cons -- or vice-versa -- but I have
> thought about it before.

Personally, I do not want anything stopping or starting services on it's
own.  That is something that I, as an administrator, should be handling.
Of course others are entitled to disagree.  :)

With that said, it may be interesting to have a knob which allows for
services to be started right away if desired by the user, and if the
port supports such a situation (ie: it does not require any
configuration after the install).  The default for the user-defined knob
would be off, for at least POLA reasons.

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


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Gerard
On Sun, 23 Mar 2008 07:48:23 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:

> On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:
> > I am almost new to portmaster, so I got a question - is there any 
> > possibility to restart installed services as in portupgrade with
> > defined BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there
> > any future plan to do so? It is annoying if I end up with some dead
> > services after upgrade just because I forgot to manualy
> > do /usr/local/etc/rc.d/some_daemon restart
> 
> This is more a complaint about the existing ports infrastructure, as
> IMHO, it's something that should be handled there and not necessarily
> by "third-party" port management utilities.
> 
> Some existing ports (such as smartmontools, i.e. smartd) do this,
> while others (such as postfix) do not.
> 
> There are pros and cons to what you want.  I myself have never managed
> to conclude if the pros outweigh the cons -- or vice-versa -- but I
> have thought about it before.

I have had serious problems in the past when ports like MySQL were
updated but not restarted. Both 'portupgrade' and 'portmanager' can
correctly handle these situations however. I have no personal
information regarding 'portmaster' other than the fact that I am
unlikely to switch to a new port's maintenance program. Nothing I have
seen indicates that it is any more reliable, secure, useful or faster
than either 'portupgrade' or 'portmanager'.

-- 
Gerard
[EMAIL PROTECTED]

There are running jobs.
Why don't you go chase them?


signature.asc
Description: PGP signature


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Miroslav Lachman

Jeremy Chadwick wrote:


On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:

I am almost new to portmaster, so I got a question - is there any 
possibility to restart installed services as in portupgrade with defined 
BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future plan 
to do so? It is annoying if I end up with some dead services after upgrade 
just because I forgot to manualy do /usr/local/etc/rc.d/some_daemon restart



This is more a complaint about the existing ports infrastructure, as
IMHO, it's something that should be handled there and not necessarily by
"third-party" port management utilities.

Some existing ports (such as smartmontools, i.e. smartd) do this, while
others (such as postfix) do not.


Yes, you are right, but there is not this functionality in current ports 
infrastructure (AFAIK), so I am happy that portupgrade does this job, 
but newer versions of portupgrade have some other "so called features", 
which I don't like, so I am trying to switch to portmaster.


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


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Miroslav Lachman

Wesley Shields wrote:

On Sun, Mar 23, 2008 at 07:48:23AM -0700, Jeremy Chadwick wrote:


On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:

I am almost new to portmaster, so I got a question - is there any 
possibility to restart installed services as in portupgrade with defined 
BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future plan 
to do so? It is annoying if I end up with some dead services after upgrade 
just because I forgot to manualy do /usr/local/etc/rc.d/some_daemon restart


This is more a complaint about the existing ports infrastructure, as
IMHO, it's something that should be handled there and not necessarily by
"third-party" port management utilities.

Some existing ports (such as smartmontools, i.e. smartd) do this, while
others (such as postfix) do not.



There is an @stopdaemon facility which can be used in the plist.  In
fact, it might be a smart idea to remove the way smartmontools does it
and replace it with @stopdaemon for consistency sake.



There are pros and cons to what you want.  I myself have never managed
to conclude if the pros outweigh the cons -- or vice-versa -- but I have
thought about it before.



Personally, I do not want anything stopping or starting services on it's
own.  That is something that I, as an administrator, should be handling.
Of course others are entitled to disagree.  :)


If I am upgrading just one port, I can restart it manualy, but if I do 
someting like `portmaster -a`, it is long running job and I do not want 
to wait and check for each port when it is right time to manualy restart 
the daemon.
So I think portmaster can have some hooks to call user defined code 
(sourced from portmaster.rc?) before or after install routine.



With that said, it may be interesting to have a knob which allows for
services to be started right away if desired by the user, and if the
port supports such a situation (ie: it does not require any
configuration after the install).  The default for the user-defined knob
would be off, for at least POLA reasons.


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


Re: portmaster and restarting of upgraded daemons

2008-03-23 Thread Wesley Shields
On Sun, Mar 23, 2008 at 04:27:21PM +0100, Miroslav Lachman wrote:
> Wesley Shields wrote:
>> On Sun, Mar 23, 2008 at 07:48:23AM -0700, Jeremy Chadwick wrote:
>> 
>>> On Sun, Mar 23, 2008 at 02:52:35PM +0100, Miroslav Lachman wrote:
>>> 
 I am almost new to portmaster, so I got a question - is there any 
 possibility to restart installed services as in portupgrade with defined 
 BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future 
 plan to do so? It is annoying if I end up with some dead services after 
 upgrade just because I forgot to manualy do 
 /usr/local/etc/rc.d/some_daemon restart
>>> 
>>> This is more a complaint about the existing ports infrastructure, as
>>> IMHO, it's something that should be handled there and not necessarily by
>>> "third-party" port management utilities.
>>> 
>>> Some existing ports (such as smartmontools, i.e. smartd) do this, while
>>> others (such as postfix) do not.
>> 
>> 
>> There is an @stopdaemon facility which can be used in the plist.  In
>> fact, it might be a smart idea to remove the way smartmontools does it
>> and replace it with @stopdaemon for consistency sake.
>> 
>> 
>>> There are pros and cons to what you want.  I myself have never managed
>>> to conclude if the pros outweigh the cons -- or vice-versa -- but I have
>>> thought about it before.
>> 
>> 
>> Personally, I do not want anything stopping or starting services on it's
>> own.  That is something that I, as an administrator, should be handling.
>> Of course others are entitled to disagree.  :)
> 
> If I am upgrading just one port, I can restart it manualy, but if I do 
> someting like `portmaster -a`, it is long running job and I do not want to 
> wait and check for each port when it is right time to manualy restart the 
> daemon.
> So I think portmaster can have some hooks to call user defined code 
> (sourced from portmaster.rc?) before or after install routine.

That's entirely up to Doug, but it could potentially be a good idea IMO.
It's kind of like the description I give below but moving it out of
ports and into portmaster, and making the code entirely user defined.

>> With that said, it may be interesting to have a knob which allows for
>> services to be started right away if desired by the user, and if the
>> port supports such a situation (ie: it does not require any
>> configuration after the install).  The default for the user-defined knob
>> would be off, for at least POLA reasons.

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


FreeBSD Port: valgrind-snapshot-352_7

2008-03-23 Thread Stephen Clark
Hello,

I am trying to use valgrind on fbsd 6.2 patch 7 to find a memory leak in
an ecpg postgresql app. When I run valgrind after a few minutes I get
this error and valgrind terminates. Ideas?

PORTNAME=   valgrind
PORTVERSION=352
PORTREVISION=   7
CATEGORIES= devel

valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb !=
((void*)0)' failed.
==4166==at 0xB802BE1F: (within /usr/local/lib/valgrind/stage2)
==4166==by 0xB802BE1E: (within /usr/local/lib/valgrind/stage2)
==4166==by 0xB802BE5D: vgPlain_core_assert_fail
(in /usr/local/lib/valgrind/stage2)
==4166==by 0xB8028091: vgPlain_arena_malloc
(in /usr/local/lib/valgrind/stage2)

sched status:

Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==4166==at 0x3C03894B: calloc
(in /usr/local/lib/valgrind/vgpreload_memcheck.so)


Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.

If that doesn't help, please report this bug to: valgrind.kde.org

In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using.  Thanks.

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


devel/pyqt4-gui fails to compile

2008-03-23 Thread David J Brooks
c++ -c -O2 -fno-strict-aliasing -pipe -I. -I../../include/Qt 
-I/usr/local/include -fno-exceptions -D_REENTRANT -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -O2 -fno-strict-aliasing -pipe -Wall -W -fPIC 
-DQT_SHARED -DQT_BUILD_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS 
-DQT_44_API_QSQLQUERY_FINISH -DQT3_SUPPORT -DQT_MOC_COMPAT 
-DQT_RASTER_IMAGEENGINE -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_MMXEXT 
-DQT_HAVE_SSE2 -DQT_NO_STYLE_MAC -DQT_NO_STYLE_WINDOWSVISTA 
-DQT_NO_STYLE_WINDOWSXP -DQ_INTERNAL_QAPP_SRC -DQT_NO_DEBUG -DQT_CORE_LIB 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/usr/local/share/qt4/mkspecs/freebsd-g++ -I. -I../../include/QtCore 
-I../../include/QtCore -I../../include -I../../include/QtGui 
-I/usr/local/include/freetype2 -I../3rdparty/harfbuzz/src -Idialogs 
-I.moc/release-shared -I/usr/local/include -I.uic/release-shared 
-I/usr/local/include -o .obj/release-shared/qcombobox.o 
widgets/qcombobox.cpp
widgets/qcombobox.cpp: In member function 'virtual void 
QComboBoxPrivateContainer::resizeEvent(QResizeEvent*)':
widgets/qcombobox.cpp:351: error: 'SH_Menu_Mask' is not a member of 'QStyle'
*** Error code 1

Stop 
in /usr/ports/x11-toolkits/qt4-gui/work/qt-x11-opensource-src-4.3.4/src/gui.
*** Error code 1

Stop in /usr/ports/x11-toolkits/qt4-gui.
*** Error code 1

Stop in /usr/ports/x11-toolkits/qt4-gui.

I wonder if anyone else has noticed the same?

David
-- 
This message was typed on location.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


open pr reminder

2008-03-23 Thread Max Brazhnikov
Hi,

I submitted ports/118269, ports/118502 during ports freeze, the PRs are 
assigned to committers acm and se. I still have no response from acm, the 
only reply from se that he's agreed to pass maintainership to me. Could 
someone please proceed these pr?

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


INDEX build failed for 5.x

2008-03-23 Thread Erwin Lansing
INDEX build failed with errors:
Generating INDEX-5 - please wait..gstreamer-plugins-taglib-0.10.7_2,3: 
"/a/erwin/tindex/portsaudio/taglib" non-existent -- dependency list incomplete
===> audio/gstreamer-plugins-taglib failed
*** Error code 1
*** Error code 1

Stop in /a/erwin/tindex/ports.
*** Error code 1

Stop in /a/erwin/tindex/ports.
1 error

Committers on the hook:
marcus mezz 

Most recent CVS update was:
U MOVED
U UPDATING
U Mk/bsd.gnome.mk
U Mk/bsd.gstreamer.mk
U accessibility/Makefile
U accessibility/accerciser/Makefile
U accessibility/accerciser/distinfo
U accessibility/accerciser/pkg-plist
U accessibility/at-spi/Makefile
U accessibility/at-spi/distinfo
U accessibility/atk/Makefile
U accessibility/atk/distinfo
U accessibility/dasher/Makefile
U accessibility/dasher/distinfo
U accessibility/dasher/pkg-plist
U accessibility/gail/Makefile
U accessibility/gail/distinfo
U accessibility/gail/pkg-plist
U accessibility/mousetweaks/Makefile
U accessibility/mousetweaks/distinfo
U accessibility/mousetweaks/pkg-descr
U accessibility/mousetweaks/pkg-plist
U accessibility/orca/Makefile
U accessibility/orca/distinfo
U accessibility/orca/pkg-plist
U accessibility/orca/files/patch-src_orca_orca.in
U archivers/file-roller/Makefile
U archivers/file-roller/distinfo
U archivers/file-roller/pkg-plist
U astro/glunarclock/Makefile
U audio/Makefile
U audio/gnome-audio/Makefile
U audio/gnome-audio/distinfo
U audio/gnome-media/Makefile
U audio/gnome-media/distinfo
U audio/gnome-media/pkg-plist
U audio/gstreamer-plugins-a52dec/Makefile
U audio/gstreamer-plugins-cdaudio/Makefile
U audio/gstreamer-plugins-cdparanoia/Makefile
U audio/gstreamer-plugins-esound/Makefile
U audio/gstreamer-plugins-faac/Makefile
U audio/gstreamer-plugins-faad/Makefile
U audio/gstreamer-plugins-flac/Makefile
U audio/gstreamer-plugins-gsm/Makefile
U audio/gstreamer-plugins-ivorbis/Makefile
U audio/gstreamer-plugins-jack/Makefile
U audio/gstreamer-plugins-ladspa/Makefile
U audio/gstreamer-plugins-lame/Makefile
U audio/gstreamer-plugins-mad/Makefile
U audio/gstreamer-plugins-musepack/Makefile
U audio/gstreamer-plugins-musicbrainz/Makefile
U audio/gstreamer-plugins-nas/Makefile
U audio/gstreamer-plugins-ogg/Makefile
U audio/gstreamer-plugins-shout2/Makefile
U audio/gstreamer-plugins-sidplay/Makefile
U audio/gstreamer-plugins-soundtouch/Makefile
U audio/gstreamer-plugins-spc/Makefile
U audio/gstreamer-plugins-speex/Makefile
U audio/gstreamer-plugins-taglib/Makefile
U audio/gstreamer-plugins-vorbis/Makefile
U audio/gstreamer-plugins-wavpack/Makefile
U audio/mpdscribble/Makefile
U audio/pulseaudio/Makefile
U audio/rhythmbox/Makefile
U audio/rhythmbox/pkg-plist
U audio/sound-juicer/Makefile
U audio/sound-juicer/distinfo
U audio/sound-juicer/pkg-plist
U databases/evolution-data-server/Makefile
U databases/evolution-data-server/distinfo
U databases/evolution-data-server/pkg-plist
U 
databases/evolution-data-server/files/patch-addressbook_backends_ldap_e-book-backend-ldap.c
U 
databases/evolution-data-server/files/patch-calendar_libical_src_libical_icaltz-util.c
U databases/evolution-data-server/files/patch-docs_reference_camel_Makefile.in
U deskutils/buoh/Makefile
U deskutils/conduit/Makefile
U deskutils/conduit/distinfo
U deskutils/conduit/pkg-plist
U deskutils/conduit/files/patch-configure
U deskutils/deskbar-applet/Makefile
U deskutils/deskbar-applet/distinfo
U deskutils/deskbar-applet/pkg-plist
U deskutils/evolution-jescs/Makefile
U deskutils/evolution-jescs/distinfo
U deskutils/gucharmap/Makefile
U deskutils/gucharmap/distinfo
U deskutils/gucharmap/pkg-plist
U deskutils/nautilus-actions/Makefile
U deskutils/nautilus-actions/distinfo
U deskutils/nautilus-actions/pkg-plist
U deskutils/nautilus-locked-folder/Makefile
U deskutils/nautilus-locked-folder/files/patch-src_Makefile.in
U deskutils/nautilus-open-terminal/Makefile
U deskutils/nautilus-open-terminal/distinfo
U deskutils/nautilus-open-terminal/pkg-plist
U deskutils/nautilus-sendto/Makefile
U deskutils/nautilus-sendto/distinfo
U deskutils/nautilus-sendto/pkg-plist
U deskutils/tomboy/Makefile
U deskutils/tomboy/distinfo
U deskutils/tomboy/pkg-plist
U devel/Makefile
U devel/anjuta/Makefile
U devel/anjuta/distinfo
U devel/anjuta/pkg-plist
U devel/anjuta/files/patch-global-tags_create_global_tags.sh
U devel/anjuta/files/patch-libanjuta_anjuta-launcher.c
U devel/bug-buddy/Makefile
U devel/bug-buddy/distinfo
U devel/bug-buddy/pkg-plist
U devel/dbus/Makefile
U devel/dbus/distinfo
U devel/dbus/pkg-install
U devel/dbus/pkg-plist
U devel/dbus/files/dbus.in
U devel/dbus/files/patch-bus_Makefile.in
U devel/dbus/files/patch-dbus_dbus-sysdeps-unix.c
U devel/gamin/Makefile
U devel/gconf2/Makefile
U devel/gconf2/distinfo
U devel/gconf2/pkg-plist
U devel/gconfmm26/Makefile
U devel/gconfmm26/distinfo
U devel/gio-fam-backend/Makefile
U devel/gio-fam-backend/distinfo
U devel/gio-fam-backend/pkg-descr
U devel/gio-fam-backend/pkg-plist
U devel/gio-fam-backend/files/patch-fam
U devel/gio-fam-backend/files/patch-gio_fam_Makefi

INDEX now builds successfully on 5.x

2008-03-23 Thread Erwin Lansing

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