I mean them downloading from the psybnc website and installing from
that tarball, I guess an option I can provide is to compile from ports
and make some sort of script to install the binaries to the user's
dir.
Chris
On Sat, 29 Jan 2005 21:10:53 +1300, Jonathan Chen [EMAIL PROTECTED] wrote:
On
I am talking about the psybnc source because its for users on the
server who cannot compile software from ports.
Chris
On Thu, 27 Jan 2005 21:03:05 -0800 (PST), Rob [EMAIL PROTECTED] wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote:
On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote:
Well it started out with me getting a complaint from a user on my
server saying he couldnt compile psybnc since I upgraded to 5.3 I told
him I would investigate when I get time, I then found out later that
ezbounce also failed (i use
On Thu, Jan 27, 2005 at 12:17:37AM -0800, Kris Kennaway wrote:
On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote:
Well it started out with me getting a complaint from a user on my
server saying he couldnt compile psybnc since I upgraded to 5.3 I told
him I would investigate when I get
On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote:
I then decided to try psybnc myself and this is what happens using
gcc 3.4.2 bundled with 5.3.
Initializing bouncer compilation
[*] Running Conversion Tool for older psyBNC Data.
tools/convconf.c: In function `cofile':
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote:
Hi,
There seems to be a bug with the gcc version of
5.3
STABLE (gcc 3.4.2), when using:
#define _GLIBCXX_DEBUG
#define _GLIBCXX_DEBUG_PEDANTIC
What are those? FreeBSD
Hi,
There seems to be a bug with the gcc version of 5.3
STABLE (gcc 3.4.2), when using:
#define _GLIBCXX_DEBUG
#define _GLIBCXX_DEBUG_PEDANTIC
I discovered this when compiling the LyX sources, and
the LyX mailing list pointed out that this is gcc/OS
FreeBSD issue.
The linking ends with
there is also a bug which prevents compiling of ezbounce and psybnc, I
wonder how much testing went into the new gcc compiler or was it just
bundled into the release, considering this is the reccommended release
for production server's now this is a bad oversight, I think the gcc
should be changed
On Wednesday, 26. January 2005 13:03, Chris wrote:
there is also a bug which prevents compiling of ezbounce and psybnc, I
wonder how much testing went into the new gcc compiler or was it just
bundled into the release, considering this is the reccommended release
for production server's now
On Wed, Jan 26, 2005 at 12:03:28PM +, Chris wrote:
there is also a bug which prevents compiling of ezbounce and psybnc, I
wonder how much testing went into the new gcc compiler or was it just
bundled into the release, considering this is the reccommended release
for production server's now
On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote:
Hi,
There seems to be a bug with the gcc version of 5.3
STABLE (gcc 3.4.2), when using:
#define _GLIBCXX_DEBUG
#define _GLIBCXX_DEBUG_PEDANTIC
What are those? FreeBSD doesn't use GLIBC, so how do you know it's a
FreeBSD bug?
Chris schrieb:
there is also a bug which prevents compiling of ezbounce and psybnc, I
wonder how much testing went into the new gcc compiler or was it just
bundled into the release, considering this is the reccommended release
for production server's now this is a bad oversight, I think the gcc
Well it started out with me getting a complaint from a user on my
server saying he couldnt compile psybnc since I upgraded to 5.3 I told
him I would investigate when I get time, I then found out later that
ezbounce also failed (i use ezbounce) on 5.3, but my binary which was
backed up from when I
13 matches
Mail list logo
