Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use. -- Chuck Haines chaines@gmail.com http://www.maxslack.com ------------------------------------------- Tau Kappa Epsilon Fraternity TKE-ZM Web Coordinator ECE Systems Administrator ------------------------------------------- AIM: CyberGrex YIM: CyberGrex_27 ICQ: 3707881 ------------------------------------------- GPG Fingerprint: 303A AB50 4EA9 70ED 2E30 2368 C9CD CCB5 4BD7 0989 GPG Key: http://www.maxslack.com/gpgkey.txt
Chuck, I moved to Linux Mandrake long ago becuase they made an effort at i586. I have no idea why Redhat/Fedora continues with i386 but I don't want to start a flame war here. If you need a compiler (i.e. you currently have none) get an RPM for fedora. You can get one from rpmfind.net. It's possible that you can find a i686 RPM (although is suspect all you will find is i386). if you don't find i686, then just take the i386 one and boot strap a new compiler. A source tar ball for gcc can be gotten from a number of mirrors. Homepage here : http://gcc.gnu.org/ Mirrors listed here : http://gcc.gnu.org/mirrors.html It's not difficult to bootstrap a compiler. If you need assistance doing this, let me know. Good luck. Jason. --- Chuck Haines <chaines@gmail.com> wrote:
Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use.
-- Chuck Haines chaines@gmail.com http://www.maxslack.com
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
You could always switch to Gentoo. Building from stage1 you have to specify the CHOST as well as make options for your processor (march=, mcp=, etc...). -Jared On Mon, 7 Mar 2005 22:17:48 -0800 (PST), J Schonber <schonm@yahoo.com> wrote:
Chuck,
I moved to Linux Mandrake long ago becuase they made an effort at i586. I have no idea why Redhat/Fedora continues with i386 but I don't want to start a flame war here.
If you need a compiler (i.e. you currently have none) get an RPM for fedora. You can get one from rpmfind.net. It's possible that you can find a i686 RPM (although is suspect all you will find is i386).
if you don't find i686, then just take the i386 one and boot strap a new compiler. A source tar ball for gcc can be gotten from a number of mirrors. Homepage here : http://gcc.gnu.org/ Mirrors listed here : http://gcc.gnu.org/mirrors.html
It's not difficult to bootstrap a compiler. If you need assistance doing this, let me know.
Good luck.
Jason.
--- Chuck Haines <chaines@gmail.com> wrote:
Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use.
-- Chuck Haines chaines@gmail.com http://www.maxslack.com
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
On Mon, Mar 07, 2005 at 11:55:00PM -0500, Chuck Haines wrote:
Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use.
You don't need a different compiler. The Fedora compiler is perfectly capable of compiling the extra instructions in the i686 instruction set. Here is what stock i386.rpm Fedora packages are compiled with: -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 The important bit is how the packages are tuned for pentium4 scheduling, since the P4 is so picky with instruction ordering (athlon couldn't care less, so these tunings matter less there). The few packages where using the extra i686 instructions actually makes sense and doesn't slow things down are already compiled that way: kernel, openssl, glibc. Other packages are .i386.rpm, but do runtime detection to enable or disable support for extra instructions, like MMX/SSE. mplayer comes to mind. In fact, the i686 kernels do runtime athlon optimizations, eliminating the need for a separately compiled athlon kernel. Don't get hung up on the .i386.rpm package naming. The RPM arch has little to do with reality these days, and there is talk about replacing it with cpu flag metadata anyway. Fedora/Red Hat hasn't run on actual i386 processors since NPTL, AFAIK. Hence, there was little perceived need or desire to change all of Fedora's RPM %{arch} tags just to provide a slightly different illusion of compatibility/optimization than we already have.
Ok, BTW, I am using gentoo that's why I want to get distcc set up. However the servers I have access to are running RHEL3 and 4. Now my question for anyone who know's distcc is that for some reason when trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686? Thanks, Chuck On Tue, 8 Mar 2005 07:32:29 -0500, Chuck R. Anderson <cra@wpi.edu> wrote:
On Mon, Mar 07, 2005 at 11:55:00PM -0500, Chuck Haines wrote:
Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use.
You don't need a different compiler. The Fedora compiler is perfectly capable of compiling the extra instructions in the i686 instruction set. Here is what stock i386.rpm Fedora packages are compiled with:
-O2 -g -pipe -m32 -march=i386 -mtune=pentium4
The important bit is how the packages are tuned for pentium4 scheduling, since the P4 is so picky with instruction ordering (athlon couldn't care less, so these tunings matter less there).
The few packages where using the extra i686 instructions actually makes sense and doesn't slow things down are already compiled that way: kernel, openssl, glibc.
Other packages are .i386.rpm, but do runtime detection to enable or disable support for extra instructions, like MMX/SSE. mplayer comes to mind. In fact, the i686 kernels do runtime athlon optimizations, eliminating the need for a separately compiled athlon kernel.
Don't get hung up on the .i386.rpm package naming. The RPM arch has little to do with reality these days, and there is talk about replacing it with cpu flag metadata anyway. Fedora/Red Hat hasn't run on actual i386 processors since NPTL, AFAIK. Hence, there was little perceived need or desire to change all of Fedora's RPM %{arch} tags just to provide a slightly different illusion of compatibility/optimization than we already have. _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Chuck Haines chaines@gmail.com http://www.maxslack.com ------------------------------------------- Tau Kappa Epsilon Fraternity TKE-ZM Web Coordinator ECE Systems Administrator ------------------------------------------- AIM: CyberGrex YIM: CyberGrex_27 ICQ: 3707881 ------------------------------------------- GPG Fingerprint: 303A AB50 4EA9 70ED 2E30 2368 C9CD CCB5 4BD7 0989 GPG Key: http://www.maxslack.com/gpgkey.txt
I would think that shouldn't matter. Its like having an "ls" command built with march=i386 as opposed to i686. It should work the same - its just optimized to _run_ on one arch or the other. -Jared On Tue, 8 Mar 2005 09:05:56 -0500, Chuck Haines <chaines@gmail.com> wrote:
Ok, BTW, I am using gentoo that's why I want to get distcc set up. However the servers I have access to are running RHEL3 and 4. Now my question for anyone who know's distcc is that for some reason when trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686?
Thanks, Chuck
On Tue, 8 Mar 2005 07:32:29 -0500, Chuck R. Anderson <cra@wpi.edu> wrote:
On Mon, Mar 07, 2005 at 11:55:00PM -0500, Chuck Haines wrote:
Does anyone know if I can get binaries so I can compile for i686 on fedora and / or rhel4. I'm trying to set up distcc, but I need i686 in order for it to work. The machines are more than compatible and I don't know what redhat hasn't finally switched over. I'm not sure I know of a single i386 machine still in use.
You don't need a different compiler. The Fedora compiler is perfectly capable of compiling the extra instructions in the i686 instruction set. Here is what stock i386.rpm Fedora packages are compiled with:
-O2 -g -pipe -m32 -march=i386 -mtune=pentium4
The important bit is how the packages are tuned for pentium4 scheduling, since the P4 is so picky with instruction ordering (athlon couldn't care less, so these tunings matter less there).
The few packages where using the extra i686 instructions actually makes sense and doesn't slow things down are already compiled that way: kernel, openssl, glibc.
Other packages are .i386.rpm, but do runtime detection to enable or disable support for extra instructions, like MMX/SSE. mplayer comes to mind. In fact, the i686 kernels do runtime athlon optimizations, eliminating the need for a separately compiled athlon kernel.
Don't get hung up on the .i386.rpm package naming. The RPM arch has little to do with reality these days, and there is talk about replacing it with cpu flag metadata anyway. Fedora/Red Hat hasn't run on actual i386 processors since NPTL, AFAIK. Hence, there was little perceived need or desire to change all of Fedora's RPM %{arch} tags just to provide a slightly different illusion of compatibility/optimization than we already have. _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Chuck Haines chaines@gmail.com http://www.maxslack.com ------------------------------------------- Tau Kappa Epsilon Fraternity TKE-ZM Web Coordinator ECE Systems Administrator ------------------------------------------- AIM: CyberGrex YIM: CyberGrex_27 ICQ: 3707881 ------------------------------------------- GPG Fingerprint: 303A AB50 4EA9 70ED 2E30 2368 C9CD CCB5 4BD7 0989 GPG Key: http://www.maxslack.com/gpgkey.txt _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
On Tue, Mar 08, 2005 at 09:05:56AM -0500, Chuck Haines wrote:
trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686?
Just create a shell script called i686-pc-linux-gnu-gcc that calls /usr/bin/gcc with -march=i686 ?
distcc knows enough to compile that stuff correctly. check out the distcc guide on gentoo's website. For all of you that don't use gentoo, all of there guides are great reading anyway. Seeing as gentoo is a source distro, most of the knowlege on the forums and guides applies to linux in general, not just their flavor. I had distcc running on a few i686's, an i586, a sparc64 and a powerpc. the x86s worked fine together, the powerpc and sparc might have had a few problems working with the group every now and again but it generally all worked. On Tue, 8 Mar 2005 09:39:40 -0500, Chuck R. Anderson <cra@wpi.edu> wrote:
On Tue, Mar 08, 2005 at 09:05:56AM -0500, Chuck Haines wrote:
trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686?
Just create a shell script called i686-pc-linux-gnu-gcc that calls /usr/bin/gcc with -march=i686 ? _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
But distcc is the one trying to call i686-pc-linux-gnu-gcc. That's where this problem came in the first place. So unless you can tell me how to change it from calling i686 to just calling gcc, I think I'll try the shell scripts. Chuck On Tue, 8 Mar 2005 10:47:51 -0500, The Freak <freak4uxxx@gmail.com> wrote:
distcc knows enough to compile that stuff correctly. check out the distcc guide on gentoo's website. For all of you that don't use gentoo, all of there guides are great reading anyway. Seeing as gentoo is a source distro, most of the knowlege on the forums and guides applies to linux in general, not just their flavor. I had distcc running on a few i686's, an i586, a sparc64 and a powerpc. the x86s worked fine together, the powerpc and sparc might have had a few problems working with the group every now and again but it generally all worked.
On Tue, 8 Mar 2005 09:39:40 -0500, Chuck R. Anderson <cra@wpi.edu> wrote:
On Tue, Mar 08, 2005 at 09:05:56AM -0500, Chuck Haines wrote:
trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686?
Just create a shell script called i686-pc-linux-gnu-gcc that calls /usr/bin/gcc with -march=i686 ? _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Chuck Haines chaines@gmail.com http://www.maxslack.com ------------------------------------------- Tau Kappa Epsilon Fraternity TKE-ZM Web Coordinator ECE Systems Administrator ------------------------------------------- AIM: CyberGrex YIM: CyberGrex_27 ICQ: 3707881 ------------------------------------------- GPG Fingerprint: 303A AB50 4EA9 70ED 2E30 2368 C9CD CCB5 4BD7 0989 GPG Key: http://www.maxslack.com/gpgkey.txt
I would think that Chuck Anderson's approach would work then. Though you might actually be able to get away with creating a link to the i386 called i686... Just a theory. -Jared On Tue, 8 Mar 2005 11:18:37 -0500, Chuck Haines <chaines@gmail.com> wrote:
But distcc is the one trying to call i686-pc-linux-gnu-gcc. That's where this problem came in the first place. So unless you can tell me how to change it from calling i686 to just calling gcc, I think I'll try the shell scripts.
Chuck
On Tue, 8 Mar 2005 10:47:51 -0500, The Freak <freak4uxxx@gmail.com> wrote:
distcc knows enough to compile that stuff correctly. check out the distcc guide on gentoo's website. For all of you that don't use gentoo, all of there guides are great reading anyway. Seeing as gentoo is a source distro, most of the knowlege on the forums and guides applies to linux in general, not just their flavor. I had distcc running on a few i686's, an i586, a sparc64 and a powerpc. the x86s worked fine together, the powerpc and sparc might have had a few problems working with the group every now and again but it generally all worked.
On Tue, 8 Mar 2005 09:39:40 -0500, Chuck R. Anderson <cra@wpi.edu> wrote:
On Tue, Mar 08, 2005 at 09:05:56AM -0500, Chuck Haines wrote:
trying to run distcc instead of it doing the gcc -march=i686, it wants to call the i686-pc-linux-gnu-gcc. Now this is a problem because the RHEL machines only have i386-pc-linux-gnu-gcc. This is the real problem I'm running in to. Does anyone know how to make distcc use gcc -march instead of trying to use the i686?
Just create a shell script called i686-pc-linux-gnu-gcc that calls /usr/bin/gcc with -march=i686 ? _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Chuck Haines chaines@gmail.com http://www.maxslack.com ------------------------------------------- Tau Kappa Epsilon Fraternity TKE-ZM Web Coordinator ECE Systems Administrator ------------------------------------------- AIM: CyberGrex YIM: CyberGrex_27 ICQ: 3707881 ------------------------------------------- GPG Fingerprint: 303A AB50 4EA9 70ED 2E30 2368 C9CD CCB5 4BD7 0989 GPG Key: http://www.maxslack.com/gpgkey.txt _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (5)
-
Chuck Haines -
Chuck R. Anderson -
J Schonberg -
Jared Greenwald -
The Freak