oscar.rodrig...@barclayscapital.com wrote:
P
----- Original Message -----
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
To: LINUX-390@VM.MARIST.EDU <LINUX-390@VM.MARIST.EDU>
Sent: Sat Jan 09 13:02:00 2010
Subject: Re: gcc 4.x.x on SLES 9
Building GCC is not difficult, but is time consuming. (MOST of the
time is simply letting the build run while you go off and have a cup
of coffee ... or a four course meal ... and dessert ... and take in a
movie.) You will, of course, need a fully functional development
environment before you can [re]build GCC.
The original poster proposes a solution to a problem, but doesn't
describe the problem.
For many purposes, gcc on something later will do as well. You could
even contemplate gcc on opensuse on an amd-64 system.
Generally, software developed on a peecee running OpenSUSE today could
be expected to run on future SLES or SLED with minimal fuss and bother.
Circumstances where this doesn't apply are fairly obvious - those that
are sensitive to the presence of specific real or virtual hardware (I'll
include all of VM that a guest can see here).
All that, and what others have said, I'd look at spec files new and old
for clues about how your new gcc should be built, but handle it outside
of package management. I'm not confident about how rpms for two
different releases of gcc could be made to live together, while building
it outside of rpm is a doddle. Just aim it for somewhere somewhat
private - /usr/local/gcc4.4 or, if Harry's the only person using it,
~/harry/gcc4.4 - and then have those who need it change their PATH to suite.
Later, removing it is as simple as "rm -rf /usr/local/gcc4.4"
You would need to update /etc/ld.so.conf or add a file to
/etc/ld.so.conf.d/ (I'm looking at RHEL-clone, SLE{S,D} might differ.
When it works, it is mostly unattended. When it doesn't work, you
will have to take the time and figure out what broke. (Maybe you
simply need to upgrade some other support utility. Who knows?)
YES, you can have two versions of GCC on the same system. No problem!
What you must do is have them in different locations. I use two
schemes for building GCC, as follows, BOTH of which place GCC apart
from the usual locations. Both of them will automagically download
the GCC source for you.
*** Using "CSCRATCH" to build GCC ***
I often use this in-place build scheme which includes GCC (and
BINUTILS, which you may also want to upgrade). It happens that the
scheme I call CSCRATCH places GCC (and BINUTILS) under /opt/gcc rather
than under /usr, so your old compiler would still be available. (And
would in fact be the default.) Be aware that this scheme will replace
most other packages IN PLACE. The fact that it relocates GCC is a
happy coincidence that I won't elaborate on today. It is presently
doing GCC 4.3.2. If you have a machine, which already has a compiler,
you are welcome to try ...
mkdir /tmp/csc
cd /tmp/csc
wget http://www.casita.net/pub/csc/makefile
make gcc.mk
make gcc.src
make gcc.cfg
make gcc.exe
sudo make gcc.ins
Then to run the new compiler, set it first in command search ...
PATH=/opt/gcc/bin:$PATH ; export PATH
You may want to do the same for BINUTILS which is at the 2.18.50.0.6
level. (And also lands safely under /opt/gcc.)
*** Using "/usr/opt" to build GCC ***
I also often use a non-intrusive scheme for building packages,
including GCC, which lets you isolate things from the operating
system. (So it does not break your box out of DPKG or RPM
management.) Someone at Rice University came up with the basic idea
years ago, and I have come to rely on it heavily. I found the build
logic for GCC 4.3.2 for this scheme and uploaded it to the web.
"/usr/opt" by design keeps everything AWAY FROM the operating system,
so here too your old compiler would still be available. (And would
again still be the default.) There are more steps (than with
CSCRATCH), but this is a much more open-ended solution.
mkdir /tmp/gcc-4.3.2
cd /tmp/gcc-4.3.2
wget http://www.casita.net/pub/gcc/gcc-4.3.2.mak
cp -p gcc-4.3.2.mak makefile
wget http://www.casita.net/pub/setup.sh
cp -p setup.sh setup
chmod a+rx setup
make source
make config
make
sudo mkdir -m 1777 /usr/opt
make install
./setup
Again, to run the new compiler, make it first in your command search ...
PATH=/usr/opt/gcc/bin:$PATH ; export PATH
You may want to do the same with "binutils-2.18.50.0.9".
I do not know how well a home-grown GCC will behave w/r/t your mixed
32-bit and 64-bit environment. Personally, I would use one of the
above methods and then rigorously test the stuff built by the new GCC.
(Most of the libraries are outside of compiler space.) Rigorous
testing is standard operating procedure, yes? :-)
-- R; <><
On Fri, Jan 8, 2010 at 11:26, rui <guidevelo...@gmail.com> wrote:
Hi all,
I am looking for gcc 4.2 onwards on sles9 x86_64. Can I get a prebuilt gcc
or do i have to build it myself? if building is the way to go, what should
be the configuration options?
I would like GCC to have 64 bit libs - having 32 bit libs is useful, but not
necessary.
Regards,
Raja
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
_______________________________________________
This e-mail may contain information that is confidential, privileged or
otherwise protected from disclosure. If you are not an intended recipient of
this e-mail, do not duplicate or redistribute it by any means. Please delete it
and any attachments and notify the sender that you have received it in error.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a
solicitation to buy or sell any securities, investment products or other
financial product or service, an official confirmation of any transaction, or
an official statement of Barclays. Any views or opinions presented are solely
those of the author and do not necessarily represent those of Barclays. This
e-mail is subject to terms available at the following link:
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the
foregoing. Barclays Capital is the investment banking division of Barclays
Bank PLC, a company registered in England (number 1026167) with its registered
off
ice at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent
from other members of the Barclays Group.
_______________________________________________
--
Cheers
John
-- spambait
1aaaa...@coco.merseine.nu z1aaaa...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
