[EMAIL PROTECTED] said:
> Here we go......
> I took the latest rh7 mysql src.rpm and rebuilt it on rh6.2, but i
> removed the berkeley db support as it wasn't aparent to me why it was
Precisely what does this mean? You removed buildrequires? Or did you change
the configuration?
If you removed Buildrequires and it builds, I reckon you're home and hosed.
> there. I talked with a co-worker and he said he recalled reading
> something about the new mysql transaction support requireng it, so
> after looking into this myself I found out he was right. I decided to
> install db1 db2 and db3, then rebuild mysql. Now, building the db1 db2
> and db3 rpms works just fine, only they won't install as per the glibc
> < 2.1.90 requirement. So I was wondering why this requirement is here.
What messages did you get? You can't figure out what they mean, and then
expect us to tell you what's wrong with even less info.
> I did search sleepycat for the answer (nothing), hmm I just tried the
> same search on google and I've found something about db2 used to be
> part of glibc. Is this maybe part of the reason?
Probably. That's why I think you might be okay if all you changed is
Buildrequires.
> Ok, I may have bitten off more than I wanted to chew at the moment
> here. :-)
[EMAIL PROTECTED] said:
> downloaded the latest version of the rh7 glibc (errata release), and
> tried to build it on rh6.2. It didn't take long until I ran into
> version requirement errors:
> checking version of gcc... egcs-2.91.66, bad checking for gnumake...
> no checking for gmake... gmake checking version of gmake... 3.78.1,
> bad <snip> configure: error: *** Some critical program is missing or
> too old. *** Check the INSTALL file for required versions. Bad exit
> status from /var/tmp/rpm-tmp.10483 (%build)
I've built a couple of gcc 2.95 src rpms on RHL 6.2. They build without
problem and (in my experience) are fine upgrades to egcs. I use it for
everything, include Kernel Building.
The only problem I've had is a couple of spastic packages that test for egcs
instead of testing for a required feature.
[EMAIL PROTECTED] said:
> At this point I'm not sure if I want to keep going to create a rh6.2
> compatible mysql rpm....unless loosing the berkeley db support won't
> hurt anything other than transaction support.
I have a RHL 5.0 system that I can install RHL 6.2 packages on. Here's how I
did it:
1) Copy the system. THis proved very important.
2) Boot the copy. Necessary to ensure I had a fallback.
3) Upgrade to the glibc 5.2 compatibility packages and glibc 2.1.
This clagged in the middle and I couldn't go forwards and I couldn't go
back. The problem apparently was a duff RPM - I'd had a few others recently
before that, but not one I built.
4) Boot the original system.
5) rpm --upgrade --force --root the same packages.
6) Boot and run the updated system for a week or so before deleting the old
system.
I imagine something like this would get you to the position where you can
install RHL 7 RPMs on 6.x, though as you observed, you're on your own.
--
Cheers
John Summerfield
http://www2.ami.com.au/ for OS/2 & linux information.
Configuration, networking, combined IBM ftpsites index.
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mail delivered to me is deemed to be intended for me, for my disposition.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
