Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

G++ an multiple architectures (solved)



On Thu, 16 Nov 2006 10:04:36 -0500 Matthew Gillen <me at mattgillen.net>
wrote:
> 
> It's certainly possible to bypass package management.  It's just more
> work and more headaches in the long run.


Agreed !!!

End-runs around package management can cause all sorts of problems that
are difficult diagnose, reproduce, document, etc.  Every one of these
sloppy quick fixes potentially ruins your ability to, at a later date,
get functional updates from rpm, yum, up2date, etc.

In the case of the Portland Group compiler that I mentioned earlier
in this thread it was relatively easy to create a local "compat" RPM
package that provided all of the contents of the directory:

    /usr/lib/gcc/i386-redhat-linux/4.1.0

that was removed by the update to 4.1.1.  In fact, such additional
"compat" RPMs are exactly what vendors such as Red Hat do when they
ship things like:

  compat-libstdc++-33-3.2.3-56.fc5

If you run "rpm -qa | grep compat" then you might find a number of
these sorts of packages already installed on your system(s).

Ed

-- 
Edward H. Hill III, PhD  |  ed at eh3.com  |  http://eh3.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20061116/a6f14b34/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org