J.L. Blom wrote:
> Hi Armin,
> Thanks for the info. I thought already that the problem is the 64-bit.
> The 32-bit emulation is a lot slower (I ran FC3 in 32-bit emulation and
> FC4 in 64-bit and the difference is rather significant). Is it difficult
> to adapt the source code to compile in 64-bi
Hi Armin,
Thanks for the info. I thought already that the problem is the 64-bit.
The 32-bit emulation is a lot slower (I ran FC3 in 32-bit emulation and
FC4 in 64-bit and the difference is rather significant). Is it difficult
to adapt the source code to compile in 64-bit mode i.e. is it more than
u
Hi,
this means that the code wont run on 64 bit system since the size of a
pointer and a int is different on 64 bit:
on 32 bit:
int: 32 bit, pointer 32 bit
on 64:
int: 32 bit, pointer 64 bit
I think the amd can also execute 32 bit code, right? So you might want
to try to compile it for 32 bit
So the compile problem on FreeBSD is due to the fact that Linux has a
global variable "timezone", which is being used by the sync engine,
whereas *BSD has a function timezone(). Anyone with experience from
*BSD: Should I make my own test for this in configure or is there a
better way?
/Bo
On Thu,
El Wed, 24 Sep 2003 22:32:33 +0200
Hubert Figuiere <[EMAIL PROTECTED]> escribió:
> According to Francisco Gómez Marín <[EMAIL PROTECTED]>:
> > I have been trying to compile multisync-0.80 on my FreeBSD 5.1 i386 box but I'm
> > having some problems:
> >
> > sync_vtype.c: In function `sync_vtype
According to Francisco Gómez Marín <[EMAIL PROTECTED]>:
> I have been trying to compile multisync-0.80 on my FreeBSD 5.1 i386 box but I'm
> having some problems:
>
> sync_vtype.c: In function `sync_vtype_convert':
> sync_vtype.c:345: warning: passing arg 2 of `libiconv' from incompatible pointe
