Matt,
Thank you for your reply. Comments below.
Matt Wilson writes:
> compat packages have to be built in the environment that they prodive
> compatibility for. In this case, compat-glibc-6.2 has to be built on
> a 6.2 system.
Don't you think this fact should be reflected in the spec file? For
example, check if you are running version 6.2? If not exit. IMHO
it should be possible to compile these libraries from an upgraded
system, if needed with the necessary old packages included!!
>
> As for the other stuff, you have some strange mix of a pinstripe and a
> rawhide, it seems. Pick one or the other, install Everything.
I'm mainly following the rawhide releases and the packages mentioned
in my mail are all from rawhide-release-20000811-1 (correction
gcc-version is 2.96-52) Regarding install everything, it's not so
easy since I'm upgrading gradually by recompiling from source,
building i686 versions if possible (its getting better and better,
thank you RH).
I'm downloading binary packages only for things that
don't compile natively. One very important point in this is that I
upgrade to a new kernel when most important packages have been
built. Therefore I cannot find problems related to dependencies on
header files of kernels not yet built or installed!!
>
> All packages except kernel (actually, kernel should work now),
> anonftp, and MAKEDEV are built as non-root here at Red Hat. We do
> massive system rebuilds all the time for toolchain regression tests.
Building as non-root has very much improved, this is very good!
>
> It doesn't make sense that you see problems. We can't reproduce it
> here, and as our package rebuilds work fine here we don't care much
> that your --rebuild doesn't work. If you have some foo package that
> doesn't rebuilt, figure out why. If you think it's a significant
> problem in the package, make a patch and submit it to bugzilla.
Regarding your statement that all packages rebuild natively at your
site without problems I don't believe. I've found errors that you
also should face, see later postings.
>
> We don't have time to go through each report and say, "update your
> kudzu" and so on.
OK, I missed to upgrade kudzu-devel (kudzu was upgraded) from
downloaded i386 files, since my native build did not work, due to
header file problems. See another posting to this list.
rpm based distributions are very sensitive to the dependencies given
in the spec files, so it's of _crucial_ importance that these are
correct. However, to my knowledge, spec file creation is a manual
process, and therefore error prone. :-(
A few additional thoughts: I'm trying to contribute to make the next RH
release as bug free as possible. Since you don't distribute i686
versions I compile my own from the source files. In this process I
find errors and (if possible) make patches. It's not my intention to
build a distribution of my own, my use is purely personal. If you are
not interested in my input, please indicate so!
>
> Matt
>
> On Thu, Aug 24, 2000 at 10:09:53AM +0200, Svante Signell wrote:
> > rpm --rebuild --target=i386 compat-glibc-6.2-2.1.3.2.src.rpm:
> > ...
> > make[1]: Leaving directory `/usr/src/redhat/BUILD/glibc-2.1.3'
> > make[1]: Entering directory `/usr/src/redhat/BUILD/glibc-2.1.3'
> > cat Versions.def glibc-compat/Versions.def >
>/usr/src/redhat/BUILD/glibc-2.1.3/build-i386-linux/Versions.allT
> > /bin/sh: invalid character 45 in exportstr for full-config-sysdirs
>> ...
> _______________________________________________
> Redhat-devel-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Best regards,
Svante Signell
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
