I highly recommend building packages using mock (unless it's a blitz
scratch build). I you really don't want to build in mock, then
yum-builddep should sort out the dependencies for you. Just make
sure that you first "yum groupinstall buildsys-build". That is the
baseline dev package group that needs to be installed on any build
system before you begin.

Gordan

On 2015-04-20 01:32, Mark Campbell wrote:
Success!  Or, at least, it's now building where it wasn't before
(hasn't completed yet).  It looks like I was indeed just missing a
package somewhere.  After a while I'd given up on getting mpich to
build, so I decided to try building ffmpeg.  I found a howto online
for ffmpeg compilation on centos, and so I went through the steps.  It
had me yum install some other packages, so I just blindly took the
whole line that it had, regardless if it was already installed or not.
 Yum came back saying the following would need to be installed:  git
nasm zlib-devel perl-Error perl-Git perl-TermReadKey libgnome-keyring
rsync.  After those installed, ffmpeg started compiling, and I decided
to see if mpich would compile this time.  And sure enough, it is!

On Sun, Apr 19, 2015 at 10:40 AM, Bjarne <[email protected]>
wrote:

I was about to write the same. The limits are for processes per user
and as I remember it is default 4096 open files/handles for a RedHat
EL/CentOS system (and also a Redsleeve system unless it has been
changed by the rootfs packager).
You should of cause check if you have that many processes open (do
a simple "ps -ef" to check).
Also check if the Makefile will make gcc compile in parallel or in
seriel (the optimizations).

BR,
Bjarne

On 18-04-2015 23:38, Gordan Bobic wrote:

That's the number of processes per user - not relevant to what I
was referring to (stack size). Must be a different problem.

_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users [1]

--

--Mark

Links:
------
[1] http://lists.redsleeve.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to