Hi,
Warren Block wrote:
A suggestion: USE_FAKE is not descriptive. It doesn't tell what is fake
or what happens. I'm not sure fake is the even the right word.
USE_FAKEROOT is better, but still ambiguous: it's not really fake, and
root can mean too many things.
I guess what I'm trying to
On Mon, Dec 14, 2009 at 3:13 PM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
Hi all,
I have updated the fakeroot patch, it now can apply on an uptodate version of
the ports.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/133815
For information the fakeroot patch is a port of
I don't know if this should be a port setting. I think this should be
a user setting. So, I think WITH_FAKE / WITH_FAKEROOT is a better
choice. Obviously ports not working with fakeroot would have to define
something like IGNORE_FAKEROOT, the same kind of variable we have for
MAKE_JOBS.
I
Kamigishi Rei (spam...@haruhiism.net) on 15/12/2009 at 22:18 wrote:
Hello,
http://media.fujibayashi.jp/software/ejabberd2-port.tar.gz (available as
a hyperlink in that post, too) for the port directory.
Please also check if you get any warning from pkg_info after the
installation, too -
I don't do enough in sed if I could figure out what it is that the broken
line is TRYING to do, I think maybe I could fix it, I HAVE used sed before, and
I know about the s command, and how it sets it's delimiters. Anyhow, here's the
broken line, and I hope my mailer doesn't decide to break
Chuck Robey wrote:
I don't do enough in sed if I could figure out what it is that the broken
line is TRYING to do, I think maybe I could fix it, I HAVE used sed before, and
I know about the s command, and how it sets it's delimiters. Anyhow, here's the
broken line, and I hope my mailer
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the trigger (an extensions.ini with only mhash causes failure, all
others minus mhash: no failure).
Same outcome on various machines, running 7.1
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the trigger (an extensions.ini with only mhash causes failure, all
others minus
2009/12/17 Raphael Becker r...@uugrn.org:
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the trigger (an extensions.ini with only mhash
On 16.12.2009 15:44, Guy Brand wrote:
The port builds and installs properly under 7.1-RELEASE/amd64/R13B02
and 9-CURRENT/amd64/R13B03. pkg_info does not complain at all. That
said portlint shows a few warnings which certainly need to be fixed.
I've corrected some errors it found, however:
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the trigger (an extensions.ini with only mhash causes failure, all
others minus
2009/12/17 Raphael Becker r...@uugrn.org:
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the trigger (an extensions.ini with only mhash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi List,
Raphael Becker wrote:
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The mhash module appears to be
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi List,
Janky Jay, III wrote:
Hi List,
Raphael Becker wrote:
On Wed, Dec 16, 2009 at 02:29:08PM -0800, Simon Shapiro wrote:
Hey,
I just updated ports on a few machines and the CLI version of php
dumps its core rather than end nicely. The
On Wed, Dec 16, 2009 at 7:53 PM, Raphael Becker r...@uugrn.org wrote:
I disabled those:
#extension=openssl.so
#extension=pdo_mysql.so
#extension=ldap.so
#extension=imap.so
#extension=mhash.so
#extension=ftp.so
#extension=curl.so
#extension=mysqli.so
If i enable any of those php will
Hello David,
On Thu, Dec 17, 2009 at 01:06:28PM +1100, David N wrote:
Thats a long list of extensions,
try adding one of them to the end of extensions.ini one by one.
The ordering of it matters, you need to re-arrange the order in which
the extensions are loaded. You may need to play
On Wed, Dec 16, 2009 at 07:40:17PM -0700, Janky Jay, III wrote:
I take this back. Removing extension=mhash.so from my
/usr/local/etc/php/extensions.ini file does, in fact, exit without a
core dump. However, mhash is required by SquirrelMail along with some of
its plugins. I'm unsure how
On Wed, Dec 16, 2009 at 08:15:40PM -0600, Matt wrote:
7 libcrypto.so.5 = /usr/local/lib/libcrypto.so.5
7 libssl.so.5 = /usr/local/lib/libssl.so.5
7 out of 8 disabled extensions depend on libcrypto.so.5 and libssl.so.5
which come from openssl-0.9.8l
You might want to check out this
On Sat, Dec 12, 2009 at 12:30:35PM +0100, Alex Dupre wrote:
have patches). To fix coredumps we need to identify the ports that
install libraries erroneously linked with libthr, that are dependencies
of php extensions. To do this task you can run the following command:
# ldd -av
I'm the port maintainer for security/barnyard2. I submitted a port
upgrade a while ago, but the committer asked me to make a change before he
would approve it. I'm not sure what to do.
The source code, when it's extracted, sets the perms on install-sh to
r--r--r. This causes an error
ok, I've marked it for deprecation early next year.
In general it's best to file PRs for things like this, so it doesn't just
get overlooked in all the mailing list traffic. Thanks.
mcl
___
freebsd-ports@freebsd.org mailing list
Kevin writes:
I've been having this problem for a couple of months now, but I
just recently decided to try to fix it. I'm running FreeBSD 6.4,
and if I try to use portupgrade to upgrade something, I get an
error (seems to be the same for other ports):
portupgrade (and -devel)
On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote:
The maintainer, ruby@, is aware of this; a check of the PR
database shows multiple open PRs, none critical but many serious
going back six months and more.
As an aside, the Severity and Priority fields have been so often abused
as to
On Wed, Dec 16, 2009 at 04:54:09PM -0500, Chuck Robey wrote:
I don't do enough in sed if I could figure out what it is that the broken
line is TRYING to do, I think maybe I could fix it, I HAVE used sed before,
and
I know about the s command, and how it sets it's delimiters. Anyhow,
24 matches
Mail list logo
