a machine will be required (always) , i think i figured it out , ineed to
compile them using *amd64 *instead of i386 .
On 2/19/08, Wojciech Puchar <[EMAIL PROTECTED]> wrote:
>
> >
> > Can anyone tell how do we handle this situation???
> >
> > Is there any way or i have to compile my code on 64
Am Dienstag, 19. Februar 2008 15:08:12 schrieb Wojciech Puchar:
> > Can anyone tell how do we handle this situation???
> >
> > Is there any way or i have to compile my code on 64 bit machine??
>
> what's a problem to compile on 64-bit machine?
Ugh, there can be lots of problems, at least if the or
Can anyone tell how do we handle this situation???
Is there any way or i have to compile my code on 64 bit machine??
what's a problem to compile on 64-bit machine?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
Binary compiled on 32 bit not running on 64 bit machine.
Actually i am using *sysctl* call and the *kinfo_proc* structure from
user.hin include/sys , size of structure on 32bit is 768 and on 64 bit
is around
1180 and thats why the call is failing and application coredumping.
Can anyone tell how d
navneet Upadhyay wrote:
On 2/18/08, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
navneet Upadhyay wrote:
On 2/18/08, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
navneet Upadhyay wrote:
Hi ,
For our product we generally compile the binaries on 32 bit
systems
and use them for both 32 and
I didnt get what do you mean.
Do you mean :
I should install lib32 on freeBSD and then rebuild my applications in order
to make it work on 32 and 64 bit systems .
rite now I have built my app on 32 bit system (which is not having lib32
installed), it works on 32 bit freebsd but fails on 64 bit s
navneet Upadhyay wrote:
> On 2/18/08, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
navneet Upadhyay wrote:
Hi ,
For our product we generally compile the binaries on 32 bit
systems
and use them for both 32 and 64 bit systems. like we have same binaries
for
32 bit and 64 bit RHEL.
We a
In response to "navneet Upadhyay" <[EMAIL PROTECTED]>:
> I checked in usr/local/ and didnt find the lib32 folder, so i guess they are
> nt installed .
>
> Why do i need them ? can u put some light on it ?
I'm not sure of the details why you need them, but no ia32 program that
I've seen runs prop
and use them for both 32 and 64 bit systems. like we have same binaries for
32 bit and 64 bit RHEL.
We are porting the product to FreeBSD and when we tried the same,
i.erunning binaries compiled on 32 bit FreeBSD
6.2 on 64 bit FreeBSD system they produce *core dump.*
no idea. i use it but rarel
Yes i am using few libs not built on FreeBSD but they work fine on 32 bit
freeBSD , so in principle they shud have the same behavior on 64 one.
On 2/18/08, Dominic Fandrey <[EMAIL PROTECTED]> wrote:
>
> navneet Upadhyay wrote:
> > Hi ,
> > For our product we generally compile the binaries
I checked in usr/local/ and didnt find the lib32 folder, so i guess they are
nt installed .
Why do i need them ? can u put some light on it ?
On 2/18/08, Norman Maurer <[EMAIL PROTECTED]> wrote:
>
>
> Am Montag, den 18.02.2008, 20:42 +0530 schrieb navneet Upadhyay:
> > it and 64 bit RHEL.
> >
>
navneet Upadhyay wrote:
Hi ,
For our product we generally compile the binaries on 32 bit systems
and use them for both 32 and 64 bit systems. like we have same binaries for
32 bit and 64 bit RHEL.
We are porting the product to FreeBSD and when we tried the same,
i.erunning binaries compi
Am Montag, den 18.02.2008, 20:42 +0530 schrieb navneet Upadhyay:
> it and 64 bit RHEL.
>
> We are porting the product to FreeBSD and when we tried the same,
> i.erunning binaries compiled on 32 bit FreeBSD
> 6.2 on 64 bit FreeBSD system they produce *core dump.*
>
>
> Any known reasons, do we h
Hi ,
For our product we generally compile the binaries on 32 bit systems
and use them for both 32 and 64 bit systems. like we have same binaries for
32 bit and 64 bit RHEL.
We are porting the product to FreeBSD and when we tried the same,
i.erunning binaries compiled on 32 bit FreeBSD
6.2
14 matches
Mail list logo