|
Home > Archive > Red Hat Configuration > March 2004 > Newbie - Config | Make | Make Install Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Newbie - Config | Make | Make Install Problem
|
|
| John M Carter 2004-03-01, 2:33 am |
| I've just downloaded glib2.2.3 (A tar.gz file) and run through the
config, make and make install which all went OK with no error messages.
I want to install another package which needs this version of glib but
when I try to install the other package it says glib is not 2.2.3. Is
this a problem with my system not recognising the later version of glib?
If so how do I get my system to recognise it?
The rpm -q says the original version of glib is still installed. If I
rpm -e the old version will my system see the newer version?
Please help a newbie!
| |
| Alexander Dalloz 2004-03-01, 9:34 am |
| On Mon, 01 Mar 2004 07:17:48 +0000 John M Carter wrote:
> I've just downloaded glib2.2.3 (A tar.gz file) and run through the
> config, make and make install which all went OK with no error messages.
> I want to install another package which needs this version of glib but
> when I try to install the other package it says glib is not 2.2.3. Is
> this a problem with my system not recognising the later version of glib?
> If so how do I get my system to recognise it?
>
> The rpm -q says the original version of glib is still installed. If I
> rpm -e the old version will my system see the newer version?
>
> Please help a newbie!
Stop this! You are destroying your total system! Hands off! If you system
still runs you have much luck so far.
glibc is not just an XY library - it is one of the most important things
on your system.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| John M Carter 2004-03-01, 7:34 pm |
| Alexander Dalloz wrote:
> On Mon, 01 Mar 2004 07:17:48 +0000 John M Carter wrote:
>
>
>
>
> Stop this! You are destroying your total system! Hands off! If you system
> still runs you have much luck so far.
>
> glibc is not just an XY library - it is one of the most important things
> on your system.
>
> Alexander
>
>
Well, thanks a bunch - not much help really. If you have nothing
positive to say then it's probably better not to reply at all. I'm not
very far into Linux so if my system crashes I'm quite happy to re-load
everything. What I really need is some help with my problem.
John
| |
| Alexander Dalloz 2004-03-01, 8:34 pm |
| On Tue, 02 Mar 2004 00:05:37 +0000 John M Carter wrote:
> Well, thanks a bunch - not much help really. If you have nothing
> positive to say then it's probably better not to reply at all. I'm not
> very far into Linux so if my system crashes I'm quite happy to re-load
> everything. What I really need is some help with my problem.
>
>
> John
It was meant as a serious warning - not more, not less.
As you did not provide any details there is nothing more to say than that
you are on the best way to damage your system. You said yourself you are a
newbie, so open your ears for the advice to have your hands off glibc.
If you really need a newer glibc than the one your Redhat release comes
with, you will have to upgrade your whole system. Exchanging just glibc
will blow you away. Erase your glibc with rpm -e and get your CDs ;)
As a general explanation why the glibc you compiled from source is not
detected by your system: rpm does not care for source installs.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| Lenard 2004-03-01, 9:33 pm |
| On Mon, 01 Mar 2004 07:17:48 +0000, John M Carter wrote:
> I've just downloaded glib2.2.3 (A tar.gz file) and run through the
> config, make and make install which all went OK with no error messages.
> I want to install another package which needs this version of glib but
> when I try to install the other package it says glib is not 2.2.3. Is
> this a problem with my system not recognising the later version of glib?
> If so how do I get my system to recognise it?
>
> The rpm -q says the original version of glib is still installed. If I
> rpm -e the old version will my system see the newer version?
The compiled glib2-2.2.3 is not in the RPM database, so the
package-manager (RPM) does not not know about the new glib. If you want to
install an updated glib then make sure you do so in a way that RPM knows
about the update. DO NOT rpm -e your installed version of glib unless you
want problems.
First get the short list of the RPM's you have already installed;
rpm -qa | grep glib | sort
Now find out the full version of glibc you have installed (very
important);
rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n' glibc
Installing the wrong update version (i386 vs i686) will cause you major
problems and headaches with your system. With this gathered information
you now have the upgrade path established. Locate and download the updated
RPM packages and all required dependencies (and dependencies of the
dependencies) for the version of Red Hat Linux you have installed needed
for the update from any of the mirror sites. If you have been keeping your
system updates current then this helps.
You might get more useful responses if you provided some information, like
the version of Red Hat Linux you have installed and the package your
attempting to install that requires the updated glib's, unless either or
both are a national secret or something!
--
Posted under the XFree86 v.1.0 license
Copyright remains with the author
| |
| John M Carter 2004-03-03, 4:34 am |
| Alexander Dalloz wrote:
> On Tue, 02 Mar 2004 00:05:37 +0000 John M Carter wrote:
>
>
>
>
> It was meant as a serious warning - not more, not less.
>
> As you did not provide any details there is nothing more to say than that
> you are on the best way to damage your system. You said yourself you are a
> newbie, so open your ears for the advice to have your hands off glibc.
>
> If you really need a newer glibc than the one your Redhat release comes
> with, you will have to upgrade your whole system. Exchanging just glibc
> will blow you away. Erase your glibc with rpm -e and get your CDs ;)
>
> As a general explanation why the glibc you compiled from source is not
> detected by your system: rpm does not care for source installs.
>
> Alexander
>
>
Alexander,
Apologies for the terse response - it was not meant to come across that
way!! Warning heeded, thanks. My system is a very basic desktop running
RH9.0 so in truth I would not be too concerned if I had to re-load it
altho' running rhn Update is a pain in the whatsit!!
I might just take a chance with the new glib but won't blame you if
things don't work out too well!!
Thanks again
John
| |
| John M Carter 2004-03-03, 4:34 am |
| Lenard wrote:
> On Mon, 01 Mar 2004 07:17:48 +0000, John M Carter wrote:
>
>
>
>
> The compiled glib2-2.2.3 is not in the RPM database, so the
> package-manager (RPM) does not not know about the new glib. If you want to
> install an updated glib then make sure you do so in a way that RPM knows
> about the update. DO NOT rpm -e your installed version of glib unless you
> want problems.
>
> First get the short list of the RPM's you have already installed;
>
> rpm -qa | grep glib | sort
>
> Now find out the full version of glibc you have installed (very
> important);
>
> rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n' glibc
>
> Installing the wrong update version (i386 vs i686) will cause you major
> problems and headaches with your system. With this gathered information
> you now have the upgrade path established. Locate and download the updated
> RPM packages and all required dependencies (and dependencies of the
> dependencies) for the version of Red Hat Linux you have installed needed
> for the update from any of the mirror sites. If you have been keeping your
> system updates current then this helps.
>
> You might get more useful responses if you provided some information, like
> the version of Red Hat Linux you have installed and the package your
> attempting to install that requires the updated glib's, unless either or
> both are a national secret or something!
>
>
>
Lenard,
Many thanks for that - it gives me a few pointers to consider. At
present the general message seems to be that I shouldn't bother unless
the software I want to install is critical for my use. It's not but I
like fiddling and learning by doing things like this and it doesn't
matter too much if I have re-load my system - it's just a bit of a nuisance!
Cheers,
John
| |
| Alexander Dalloz 2004-03-03, 10:34 am |
| On Wed, 03 Mar 2004 09:19:26 +0000 John M Carter wrote:
[ snip ]
> Apologies for the terse response - it was not meant to come across that
> way!! Warning heeded, thanks. My system is a very basic desktop running
> RH9.0 so in truth I would not be too concerned if I had to re-load it
> altho' running rhn Update is a pain in the whatsit!!
> I might just take a chance with the new glib but won't blame you if
> things don't work out too well!!
> Thanks again
>
> John
Ok, John, if you try to learn by faults and do not mind about destroyed
systems, all is ok  I just warned because most people would heavily
dislike to make their system a dead fish.
If you need a newer glibc for your application than the one shipped with
RH9 you should choose Fedora (fedora.redhat.com). It's free and you can
treat it as RH10 actually. Fedora Core 2 will come out ~ beginning of May
and will be something like RH11. Fedora does not need an account at RHN
and can be updated using several mirror servers. Much more handy.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| Lenard 2004-03-03, 2:35 pm |
| On Wed, 03 Mar 2004 09:28:34 +0000, John M Carter wrote:
> Lenard,
>
> Many thanks for that - it gives me a few pointers to consider. At
> present the general message seems to be that I shouldn't bother unless
> the software I want to install is critical for my use. It's not but I
> like fiddling and learning by doing things like this and it doesn't
> matter too much if I have re-load my system - it's just a bit of a
> nuisance!
After seeing your other posts to this thread all you need do is;
First get the short list of the RPM's you have already installed;
rpm -qa | grep glibc | sort
Now find out the full version of glibc you have installed (very
important);
rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n' glibc
Then go here and download the updated RPM's for RH9;
https://rhn.redhat.com/errata/RHSA-2003-325.html
Make sure you get the glibc RPM's and maybe both the nscd and nptl-devel
RPMs if needed. Use the the rpm -q <package_name> to figure this out.
/Soap Box Time--Start
FYI: To those following this thread. Yes it can be very dangerous to
update glibc without the proper considerations taken to plan the update,
but it not impossible and in some cases it is recommended. Case in point
RHSA-2003-325 (the link above). And for those that are still unsure;
$ rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n' |
grep glibc | sort
glibc-2.3.3-12.i686.rpm
glibc-common-2.3.3-12.i386.rpm
glibc-devel-2.3.3-12.i386.rpm
glibc-headers-2.3.3-12.i386.rpm
glibc-kernheaders-2.4-8.10.i386.rpm
$ rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n' |
grep nscd | sort
nscd-2.3.3-8.i386.rpm
$ cat /etc/redhat-release
Red Hat Linux release 9 (Shrike)
Keeping your system update to the current release level is important for
both security and bug fixes. I do not recommend updating to the bleeding
edge, but updating to the currently released errata is a good idea. As
long as the distro is being maintained by Red Hat one can check every so
often here; http://www.redhat.com/apps/support/errata/ to keep the
system(s) current. And here for a least six months after the EOL;
http://www.redhat.com/support/errata/archives/
Also there is the Fedora Legacy Project for Red Hat Linux 7.2, 7.3 and 8.0
currently and soon for Red Hat Linux 9 when it reaches EOL (End Of Life).
http://www.fedoralegacy.org/#main
/Soap Box Time--End
--
Posted under the XFree86 v.1.0 license
Copyright remains with the author
| |
|
|
|
|
|