On 2015-04-17 09:07, Jacco Ligthart wrote:
On 04/17/2015 03:30 AM, Mark Campbell wrote:
Gordon,
I haven't done anything with either of those. Beyond it starting out
as a bare bone RSEL 7 image, me installing the RPi2 kernel from RSEL
6, and then me installing packages via yum as I found the build
failing due to missing packages, I've done virtually no customization
to the environment. That's why I figured there might've been some
system variable that may have been affecting this somehow.
Perhaps the issue is still one of me not having the necessary packages
installed, it's just hiding under a misleading error? Jacco, would it
be terribly inconvenient if I could get a list of packages you have
installed on your rpi2? Maybe if I replicate what you have installed,
my problem will go away?
:) *all*
This is the test system I use to verify that packages are installable.
Another way could be to download the mpich src.rpm and install the
rpm-build rpm.
Then try "rpmbuild --rebuild mpich*src.rpm". If you miss packages it
will tell you which ones you miss.
Actually, having too many packages installed could be just as
problematic as having too few. I recall I ran into this problem
during the original bootstrapping build of RSEL6. I cannot
remember which package was experiencing this problem, but in
a nutshell, what was happening is that the ./configure script
was checking for packages not in the BuildRequires list, and
when it found them, it decided to build against them, except
that build path was actually broken.
While problems like this annoy the living daylights out of
me, and are, IMO, bugs that should be fixed, it is nearly
impossible to get any traction upstream to having ANY bug,
including blatant kernel mispatch bugs, even looked at if
it doesn't get tripped in the primary architecture build
or built on a build system that only installs minimal
packages for each build root.
So while I would love to have time to go on a crusade to
identify and fix all such things, the reality of the
situation is that the most sane course of action is to
follow the path of least resistance and stick with building
in a mock-like minimal chroot environment.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
