Re: Ports and 64-bit Processors
you may just copy binaries onto amd64 system and they will work in 32-bit mode. As long as you also copy the 32-bit libraries that they need! "binaries" means both. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
On Fri, Aug 29, 2008 at 08:48:24PM +0200, Wojciech Puchar wrote: > > > > AFAIK, it is not as much a question of ports being broken, but there are > > some ports that have 'ONLY_FOR_ARCHS=i386' set, e.g. because they are > > binary-only ports (e.g. flash plugin, nvidia driver) or because they > > contain i386 assembly code or because the code contains assumptions that > > are true on i386 but not on amd64 (like the size of a pointer being > > equal to the size of an integer). > > you may just copy binaries onto amd64 system and they will work in 32-bit > mode. As long as you also copy the 32-bit libraries that they need! Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpzibqfhNBdc.pgp Description: PGP signature
Re: Ports and 64-bit Processors
On Fri, Aug 29, 2008 at 10:34 AM, sergio lenzi <[EMAIL PROTECTED]> wrote: > Em Sex, 2008-08-29 às 10:57 -0400, Bill Moran escreveu: > >> In response to "FreeBSD Questions" <[EMAIL PROTECTED]>: >> >> > FreeBSD has supported 64-bit architectures for a while now... Alpha >> > and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 >> > architecture. I'm surprised to hear so many of you say that certain >> > ports are broken on AMD64. I would think if they worked on other >> > 64-bit processors they'd work on AMD64. Were the ports that are >> > broken on AMD64 also broken on those other architectures, too? >> >> Most of the ports I've had problems with are desktop applications. >> Stuff that doesn't often get installed/used on 64 bit. It's been a >> while since we've tried (about 1 year) but Gnome was pretty unstable >> on 64 bit at the time. > > I have had good experiences with gnome 2.22 and amd64 in produtcion > systems > running on dell poweredge with 4core cpus (4 logical processors) 2Gb of > memory, > 120 users using gnome, evolution, openoffice-3, epiphany, pidgin, > java... postgres > servers and a callcenter dial apllication, that needs an asterisk 1.4.21 > (on 64 bit too...) > runs about 24X7 the machine have somestimes 1200 process running full > time > alll the clients are thin clients (amd geode, 32 bits, 64mb)... 100 > mbits ethernet > with NO Backup... uptime is 38 days Yes... it needs more memory... > === > last pid: 65631; load averages: 0.89, 1.04, 1.07 up 38+05:23:12 > 12:23:15 > 824 processes: 1 running, 814 sleeping, 9 stopped > CPU states: 2.8% user, 0.0% nice, 1.0% system, 0.5% interrupt, 95.7% > idle > Mem: 1147M Active, 100M Inact, 601M Wired, 92M Cache, 213M Buf, 12M Free > Swap: 8192M Total, 1955M Used, 6237M Free, 23% Inuse, 12K In > === > we use it in our notebooks too (dell, acer, hp...) several ones about > 20... 64 bits amd64 > running on amd hardware or D series intel... > > The 32 bit version we use on the geode hardware.. but stays in the 64 > bit machine exported > in a nfs... > > Runs fine... > > Sergio > Hi How do you set up those clients. Im a bit curious ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
AFAIK, it is not as much a question of ports being broken, but there are some ports that have 'ONLY_FOR_ARCHS=i386' set, e.g. because they are binary-only ports (e.g. flash plugin, nvidia driver) or because they contain i386 assembly code or because the code contains assumptions that are true on i386 but not on amd64 (like the size of a pointer being equal to the size of an integer). you may just copy binaries onto amd64 system and they will work in 32-bit mode. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
Roland Smith writes: > To see which ports are restricted to certain architectures, try the > following command: > > find /usr/ports -type f -name Makefile -exec grep -H ONLY_FOR_ARCH {} \;|less This returned 643 entries, of which 29 listed a reason. Six of those use assembler code. 122 contain the string "linux". One is listed as alpha only; another, as sparc only. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
On Fri, Aug 29, 2008 at 10:44:10AM -0400, FreeBSD Questions wrote: > FreeBSD has supported 64-bit architectures for a while now... Alpha > and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 > architecture. I'm surprised to hear so many of you say that certain > ports are broken on AMD64. AFAIK, it is not as much a question of ports being broken, but there are some ports that have 'ONLY_FOR_ARCHS=i386' set, e.g. because they are binary-only ports (e.g. flash plugin, nvidia driver) or because they contain i386 assembly code or because the code contains assumptions that are true on i386 but not on amd64 (like the size of a pointer being equal to the size of an integer). To see which ports are restricted to certain architectures, try the following command: find /usr/ports -type f -name Makefile -exec grep -H ONLY_FOR_ARCH {} \;|less > I would think if they worked on other 64-bit processors they'd work on > AMD64. Were the ports that are broken on AMD64 also broken on those > other architectures, too? -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpu8j2C2riZT.pgp Description: PGP signature
Re: Ports and 64-bit Processors
and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 architecture. I'm surprised to hear so many of you say that certain ports are broken on AMD64. I would think if they worked on other 64-bit processors they'd work on AMD64. Were the ports that are broken on AMD64 also broken on those other architectures, too? no idea. all ports i use are not broken :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
Em Sex, 2008-08-29 às 10:57 -0400, Bill Moran escreveu: > In response to "FreeBSD Questions" <[EMAIL PROTECTED]>: > > > FreeBSD has supported 64-bit architectures for a while now... Alpha > > and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 > > architecture. I'm surprised to hear so many of you say that certain > > ports are broken on AMD64. I would think if they worked on other > > 64-bit processors they'd work on AMD64. Were the ports that are > > broken on AMD64 also broken on those other architectures, too? > > Most of the ports I've had problems with are desktop applications. > Stuff that doesn't often get installed/used on 64 bit. It's been a > while since we've tried (about 1 year) but Gnome was pretty unstable > on 64 bit at the time. I have had good experiences with gnome 2.22 and amd64 in produtcion systems running on dell poweredge with 4core cpus (4 logical processors) 2Gb of memory, 120 users using gnome, evolution, openoffice-3, epiphany, pidgin, java... postgres servers and a callcenter dial apllication, that needs an asterisk 1.4.21 (on 64 bit too...) runs about 24X7 the machine have somestimes 1200 process running full time alll the clients are thin clients (amd geode, 32 bits, 64mb)... 100 mbits ethernet with NO Backup... uptime is 38 days Yes... it needs more memory... === last pid: 65631; load averages: 0.89, 1.04, 1.07 up 38+05:23:12 12:23:15 824 processes: 1 running, 814 sleeping, 9 stopped CPU states: 2.8% user, 0.0% nice, 1.0% system, 0.5% interrupt, 95.7% idle Mem: 1147M Active, 100M Inact, 601M Wired, 92M Cache, 213M Buf, 12M Free Swap: 8192M Total, 1955M Used, 6237M Free, 23% Inuse, 12K In === we use it in our notebooks too (dell, acer, hp...) several ones about 20... 64 bits amd64 running on amd hardware or D series intel... The 32 bit version we use on the geode hardware.. but stays in the 64 bit machine exported in a nfs... Runs fine... Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports and 64-bit Processors
In response to "FreeBSD Questions" <[EMAIL PROTECTED]>: > FreeBSD has supported 64-bit architectures for a while now... Alpha > and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 > architecture. I'm surprised to hear so many of you say that certain > ports are broken on AMD64. I would think if they worked on other > 64-bit processors they'd work on AMD64. Were the ports that are > broken on AMD64 also broken on those other architectures, too? Most of the ports I've had problems with are desktop applications. Stuff that doesn't often get installed/used on 64 bit. It's been a while since we've tried (about 1 year) but Gnome was pretty unstable on 64 bit at the time. Can't say if this is universal across all 64 bit platforms. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ports and 64-bit Processors
FreeBSD has supported 64-bit architectures for a while now... Alpha and UltraSPARC come to mind--even if Alpha is no longer a Tier 1 architecture. I'm surprised to hear so many of you say that certain ports are broken on AMD64. I would think if they worked on other 64-bit processors they'd work on AMD64. Were the ports that are broken on AMD64 also broken on those other architectures, too? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"