I'm upgrading a 7.3 -STABLE installation to 8.x, then 9- Stable over the
next few days. The hardware is a Dell 2950 that is capable of running
64 bit FreeBSD. The original installation was i386 32 bit and that is
what it is running now.
Will the buildworld --- buildkernel KERNCONF=FOO64
It has been done, it's just rally not recommended.
Sorry, don't know what was exact procedure/
if it works currently.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/32-bit-to-64-bit-tp5722481p5722485.html
Sent from the freebsd-questions mailing list archive at Nabble.com
On 6/27/2012 9:37 AM, Tim Kellers wrote:
Will the buildworld --- buildkernel KERNCONF=FOO64 allow a 32 bit
installation to build a 64 bit kernel? I'd like to upgrade this machine
to 64 bit AMD and I'd prefer not to do it from a DVD if I can do it from
source. Has anyone tried this and
On Wed, Jun 27, 2012 at 4:37 PM, Tim Kellers timot...@devel.njit.eduwrote:
I'm upgrading a 7.3 -STABLE installation to 8.x, then 9- Stable over the
next few days. The hardware is a Dell 2950 that is capable of running 64
bit FreeBSD. The original installation was i386 32 bit and that is what
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
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
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 original
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 bit
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
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 have
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
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 have to compile binaries on 64 bit machine.
Thanks,
Do you have the lib32's installed ?
bye
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 on 64 bit FreeBSD system they produce *core dump
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 have to compile
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
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
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
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.*
Any known reasons, do we have to compile binaries on 64
18 matches
Mail list logo
