> Maybe someone has similar feeling, so I thought maybe
> its not that bad idea to create GIMP 2.4 port that keep all of the
> nice features destroyed by a new design team in GIMP 2.6?
Haven't you tried to take in contact with GIMP developers?
--
Regards,
Konstantin
Hello,
I understand there were a few bugs with ossec v2.5... v2.5.1 has now
been released. Where are we at with maintenance for this port? Would it
be better if I submitted a patch?
Many Thanks
Jake
On Tue, 2010-10-05 at 21:47 +0100, Jake Smith wrote:
> Hi,
>
> When can we expect security/osse
Good day!
I'm trying to build ejabberd but to not avail:
In file included from sha_drv.c:23:
/usr/include/openssl/md2.h:64:2: error: #error MD2 is disabled.
gmake[1]: *** [../sha_drv.so] Ошибка 1
gmake[1]: Leaving directory
`/usr/ports/net-im/ejabberd/work/ejabberd-2.1.5/src/tls'
gmake: *** [a
Hello,
Seeing this on an amd64 box when doing a fresh Xorg build:
===> Building for dri-7.6.1,2
gmake[1]: Entering directory `/usr/ports/graphics/dri/work/Mesa-7.6.1/src'
Making sources for autoconf
gmake[2]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-7.6.1/src/glx/x11'
rm -f depend
t
22.10.2010 23:07, Chuck Swiger пишет:
On Oct 22, 2010, at 11:44 AM, Ruslan Mahmatkhanov wrote:
In file included from sha_drv.c:23:
/usr/include/openssl/md2.h:64:2: error: #error MD2 is disabled.
gmake[1]: *** [../sha_drv.so] Ошибка 1
gmake[1]: Leaving directory
`/usr/ports/net-im/ejabberd/work/
On Oct 22, 2010, at 12:19 PM, Ruslan Mahmatkhanov wrote:
> It works. Thanks!
Very good; you're most welcome
Regards,
--
-Chuck
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
This is a heads-up for those who might configure their systems in this way.
First some background. I normally build ports in a jail, then copy them
($LOCALBASE, package databases, etc) to the various systems in my
infrastructure -- it's all scripted (differences in config files are
maintained t
Folks,
It would appear that ever since 3.2.8_1 of virtualbox-ose, a number of
additions were made to unconditionally enable some kind of hardware
acceleration in the UI.
This completely breaks the UI with a variety of QT errors, when running on a
remote X11 displays, so far I've tested X11.app
On Oct 22, 2010, at 11:44 AM, Ruslan Mahmatkhanov wrote:
> In file included from sha_drv.c:23:
> /usr/include/openssl/md2.h:64:2: error: #error MD2 is disabled.
> gmake[1]: *** [../sha_drv.so] Ошибка 1
> gmake[1]: Leaving directory
> `/usr/ports/net-im/ejabberd/work/ejabberd-2.1.5/src/tls'
> gmake
On Fri, 22 Oct 2010 15:02:20 -0500, Ade Lovett wrote:
> Folks,
>
> It would appear that ever since 3.2.8_1 of virtualbox-ose, a number
> of additions were made to unconditionally enable some kind of hardware
> acceleration in the UI.
>
> This completely breaks the UI with a variety of QT errors,
On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote:
> Could you please post that errors?
freebsd% setenv DISPLAY remote:0
freebsd% VirtualBox
Wait for UI to pop up, click on 'Settings' for any virtual host, VirtualBox
crashes with:
Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid c
On Fri, 22 Oct 2010 12:42:19 -0700
Cy Schubert wrote:
[ .. ]
> If
> /usr/local is mounted from a ZFS filesystem, it works. (Not sure
> about NFS but I suspect it might work too,)
[ .. ]
Yep.. I run mine with /usr.local being on ZFS.
--
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intel
On Fri, Oct 22, 2010 at 5:04 PM, Ade Lovett wrote:
>
> On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote:
> > Could you please post that errors?
>
> freebsd% setenv DISPLAY remote:0
> freebsd% VirtualBox
>
> Wait for UI to pop up, click on 'Settings' for any virtual host, VirtualBox
> crashes
2010/10/21 Вадим Петряев :
> Hello!
>
>
>
> Transmission was two times released after version 2.04
> https://trac.transmissionbt.com/roadmap?show=completed
>
> 10 October released 2.10 and 17 October released 2.11
>
> May be you need some help for port maintenance?
>
> As I understand, this port re
I was going through bsd.port.mk to learn how the ports system works.
It seems quite complex - partly due to all the different
configurations that need to be supported.
1) I noticed some hacks that were in place in 2004 and I was curious
if they were fixed by now, and if so if the hacks should be
I was going through bsd.port.mk to learn how the ports system works.
...
Sorry - my initial subject was wrong - I had an extra s.
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubs
16 matches
Mail list logo
