On Tue, Jun 22, 2004 at 03:09:18PM +0200, Bjoern Koenig wrote:
> Hello,
>
> first of all:
>
> THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
> (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
> DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
> BEWARE OF DOG. SLIPPERY WHEN WET.
Right, but t
On Wednesday 16 June 2004 09:55 pm, Roger Merritt wrote:
> I hadn't updated my world for quite a while, so I ran cvsup to make
> sure I had the latest modifications to the code and then tried to run
> "make buildworld". Failed. Tried again, failed. Went to the file
> where the build failed, didn't
> Well...
>
> It appears that the mnoGoSearch option for the php-cli is not working
> correctly. I recompiled the mnogosearch port then tried to compile php4
> WITH_MNOGOSEARCH=ON and it resulted in the libtool link error described
> in previous posts.
>
> the lang/php4 port appears to com
On Tue, 22 Jun 2004, Bjoern Koenig wrote:
Hello,
first of all:
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
(READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
BEWARE OF DOG. SLIPPERY WHEN WET.
My experience:
I had much less problems with unionfs
At 1:32 PM -0700 2004/06/21, Kris Kennaway wrote:
On Mon, Jun 21, 2004 at 10:05:29AM -0400, Chris Pepper wrote:
At 12:01 AM -0700 2004/06/21, Kris Kennaway wrote:
> > [EMAIL PROTECTED] XFree86-4-libraries]# make clean USE_LIBTOOL_VER=15
>
>USE_* are not to be specified by the user, they're only
Well...
It appears that the mnoGoSearch option for the php-cli is not working
correctly. I recompiled the mnogosearch port then tried to compile php4
WITH_MNOGOSEARCH=ON and it resulted in the libtool link error described
in previous posts.
the lang/php4 port appears to compile successfully wi
Sayid Munawar wrote:
Yes... i received the same error and i posted here too with the subject:
libtool problem or SMP problem or port problem or what?
I have tried to cvsup my ports collection yesterday, but the problem
persist. I think one of the php's feature (WITH_ ) is leading to this
problem.
Hello,
first of all:
THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED
(READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT,
DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK.
BEWARE OF DOG. SLIPPERY WHEN WET.
My experience:
I had much less problems with unionfs -b, even with FreeBSD 4.10, to mount
