[xdebug-general] Re: xdebug 2-csv freebsd port

is this patch for CVS? or the bundled 2.0.0 beta 2 source? i'm not
sure where to apply it.

I applied the previous patches to 2.0.0 beta 2 and it worked, but the
chacegrind files will not open in WinCacheGrind. Gives a bad int
error.

I'm using FreeBSD 5.3-RELEASE amd64 SMP

On Fri, 18 Mar 2005 02:39:48 +0100, Roman Neuhauser <neuhauser[@]chello.cz> wrote:
> # yoel.h.k[@]gmail.com / 2005-03-16 18:38:47 -0500:
> > On Wed, 16 Mar 2005 23:30:36 +0100, Roman Neuhauser <neuhauser[@]chello.cz> wrote:
> > > # derick[@]xdebug.org / 2005-03-16 20:19:16 +0100:
> > > > On Wed, 16 Mar 2005, yoel k wrote:
> > > >
> > > > >any plans on making a current xdebug freebsd port?
> > > >
> > > > I don't know how to do it myself, but I CC-ed the port maintainer.
> > > > Perhaps he can make one for 2.0.0beta2.
> > >
> > > Like I said a few days ago, I'll update the port when/if people
> > > request it. So it's the time now. :)
> >
> > if you'd be able to make a port that would be greatly appreciated!
> >
> > i was unable to compile it on freebsd amd64. tried a few different patches.
>
> I'm attaching a diff against devel/php-xdebug that brings it to
> 2.0.0beta2. I haven't tested it beyond installing it, and checking
> it appears in php -m / php -i (with 5.0.3 (cli)), both on an 32bit
> box.
>
> It'll take a few days before I get around to actually using it on
> (at least some of) 4.x/i386, 5.x/i386, CURRENT/amd64, so I'm
> all ears for possible bug reports.
>
> The port doesn't install debugclient, I've created a separate port
> I'll post here in another email.
>
> --
> How many Vietnam vets does it take to screw in a light bulb?
> You don't know, man. You don't KNOW.
> Cause you weren't THERE. http://bash.org/?255991
>
>
>
Received on Fri Mar 18 2005 - 02:50:39 GMT