Hi,
I updated sdl12 to the latest stable version 1.2.11 on my system and
thought, that it might be a good thing to incorporate the both related
reports ports/99943 and ports/70900 (which can be closed then).
As both ports/70900 suggests, the patch matches the SDL version 1.2. So
instead of using
On Thu, 31 Aug 2006 10:53:50 +0200
Marcus von Appen <[EMAIL PROTECTED]> mentioned:
> Hi,
>
> I updated sdl12 to the latest stable version 1.2.11 on my system and
> thought, that it might be a good thing to incorporate the both related
> reports ports/99943 and ports/70900 (which can be closed the
* Patrick Lamaizière <[EMAIL PROTECTED]>:
> The port lang/smarteiffel 1.2r7 is marked BROKEN : does not fetch.
> It is ok now, the file is online (same URL).
I fixed this, thanks!
Volker
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.o
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Arts++ configure 1.1.a11, which was
generated by GNU Autoconf 2.53. Invocation command line was
$ ./configure --enable-shared --prefix=/usr/local
i386
Under no circumstances should a port install world-writable
files or directories. In most cases this opens the system to all
kinds of attacks. A simple grep brings the following list of
makefiles to attention. I imagine that samba ports are
somehow justified, as for the other ones, I hope secteam
On Thu, Aug 31, 2006 at 06:15:18PM +0400, Andrew Pantyukhin wrote:
> Under no circumstances should a port install world-writable
> files or directories. In most cases this opens the system to all
> kinds of attacks. A simple grep brings the following list of
> makefiles to attention. I imagine that
2006/8/31, Ruslans Baidaks <[EMAIL PROTECTED]>:
It was created by Arts++ configure 1.1.a11, which was
generated by GNU Autoconf 2.53. Invocation command line was
configure:1609: checking for C compiler default output
configure:1612: gcc295 -O2 -pipe -march=pentium4 conftest.c >&5
cc1: bad v
Andrew Pantyukhin ha scritto:
> Under no circumstances should a port install world-writable
> files or directories.
> www/eaccelerator/Makefile
Where? I suspect you grep'ed 777 inside Makefiles, but in eaccelerator
there is indeed a 's/777/755/' substitution :-)
--
Alex Dupre
___
On 8/31/06, Alex Dupre <[EMAIL PROTECTED]> wrote:
Andrew Pantyukhin ha scritto:
> Under no circumstances should a port install world-writable
> files or directories.
> www/eaccelerator/Makefile
Where? I suspect you grep'ed 777 inside Makefiles, but in eaccelerator
there is indeed a 's/777/755/'
On Thu, Aug 31, 2006 at 01:18:22PM +0400, Stanislav Sedov wrote:
> On Thu, 31 Aug 2006 10:53:50 +0200
> Marcus von Appen <[EMAIL PROTECTED]> mentioned:
>
> > Hi,
> >
> > I updated sdl12 to the latest stable version 1.2.11 on my system and
> > thought, that it might be a good thing to incorporate
On Thu, 31 Aug 2006 11:17:10 -0400
Kris Kennaway <[EMAIL PROTECTED]> mentioned:
> Thanks, let us know when you have something ready for testing,
> although it will probably have to wait until after the 6.2 release
> cycle.
>
> Kris
I've entire patch already available.
http://mbsd.msk.ru/dist/sd
On Thu, 31 Aug 2006 18:51:27 +0400
"Andrew Pantyukhin" <[EMAIL PROTECTED]> mentioned:
> On 8/31/06, Alex Dupre <[EMAIL PROTECTED]> wrote:
> > Andrew Pantyukhin ha scritto:
> > > Under no circumstances should a port install world-writable
> > > files or directories.
> >
> > > www/eaccelerator/Makef
On Thu, Aug 31, 2006 at 08:20:06PM +0400, Stanislav Sedov wrote:
> On Thu, 31 Aug 2006 11:17:10 -0400
> Kris Kennaway <[EMAIL PROTECTED]> mentioned:
>
>
> > Thanks, let us know when you have something ready for testing,
> > although it will probably have to wait until after the 6.2 release
> > cy
On Thu, 31 Aug 2006 20:34:21 +0400
Stanislav Sedov <[EMAIL PROTECTED]> mentioned:
>
> Hmm, strange method... In fact, most of port you listed are harmless.
>
Sorry, now I see that the word 'most' isn't applicable here.
My apologizes.
--
Stanislav Sedov MBSD labs, Inc. <[EMAIL P
Hi. I'm trying to compile ruby (my system is up to date stable 6.1). And
it fails saying:
panix# cd /usr/ports/lang/ruby18
panix# make
NOTE:
You can enable pthread support by defining WITH_PTHREADS variable,
but not recommended since this might break some ruby apps.
=> ruby/ruby-1.8.5.tar.gz is
I don't know who is the correct person, or even if there
is a ports maintainer for the linphone port. A friend of
mine told me he is unable to build the port in 6.1-STABLE
since so many other dependencies have changed, or need to
change. Is there any feedback on this situation? I had
no problem
On, Thu Aug 31, 2006, Stanislav Sedov wrote:
> On Thu, 31 Aug 2006 11:17:10 -0400
> Kris Kennaway <[EMAIL PROTECTED]> mentioned:
>
>
> > Thanks, let us know when you have something ready for testing,
> > although it will probably have to wait until after the 6.2 release
> > cycle.
> >
> > Kris
On Thu, 31 Aug 2006 23:10:15 +0200
Marcus von Appen <[EMAIL PROTECTED]> mentioned:
>
> No, it won't, if I see that right.
>
> DIRFB "Include support for DirectFB" Off \
>
> and
> .if defined(WITH_DIRECTFB)
> LIB_DEPENDS+= directfb-0.9.16:${PORTSDIR}/devel/directfb
> ...
>
>
On Thu, 31 Aug 2006 16:33:29 -0300
Carlos Fernando Assis Paniago <[EMAIL PROTECTED]> mentioned:
> Hi. I'm trying to compile ruby (my system is up to date stable 6.1). And
> it fails saying:
>
> panix# cd /usr/ports/lang/ruby18
> panix# make
>
> NOTE:
> You can enable pthread support by defining
On, Thu Aug 31, 2006, Stanislav Sedov wrote:
> On Thu, 31 Aug 2006 23:10:15 +0200
> Marcus von Appen <[EMAIL PROTECTED]> mentioned:
> >
> > No, it won't, if I see that right.
> >
> > DIRFB "Include support for DirectFB" Off \
> >
> > and
> > .if defined(WITH_DIRECTFB)
> > LIB_DEP
On Thu, Aug 31, 2006 at 10:19:24AM -0400, Kris Kennaway wrote:
> On Thu, Aug 31, 2006 at 06:15:18PM +0400, Andrew Pantyukhin wrote:
> > Under no circumstances should a port install world-writable
> > files or directories. In most cases this opens the system to all
> > kinds of attacks. A simple gre
Jiawei Ye wrote:
> I can see that postgresql requires LOGIN, but jabberd is BEFORE:LOGIN,
> what is the proper solution?
If I understand correctly, pgsql runs as an unprivileged user, which means
it needs to REQUIRE LOGIN. OTOH, there is no reason that jabberd should run
BEFORE LOGIN, and I suspe
On Fri, 1 Sep 2006 00:27:01 +0200
Marcus von Appen <[EMAIL PROTECTED]> mentioned:
>
> Why do you place the examples beneath PORTDOCS (default
> /usr/locals/share/doc) and not into EXAMPLESDIR as done before (default
> /usr/local/share/examples)?
>
No, I've placed it into EXAMPLESDIR. You've p
On 9/1/06, Doug Barton <[EMAIL PROTECTED]> wrote:
ports/net-im/jabber/files/jabberd.sh.in does not have that line, so I am
wondering what port you're working with here.
Well, it is here in mine:
cat /usr/ports/net-im/jabberd/files/jabberd.sh.in
#!/bin/sh
# Start or stop jabberd
# $FreeBSD: por
24 matches
Mail list logo