Minh Nguyen wrote:
Hi Richard,
On Wed, Feb 17, 2010 at 1:41 AM, rvaug...@gmail.com wrote:
It would be good if we could see a copy of config.log.
Install.log is over 25K lines, too large for posting.
See it here: http://www.physics.rutgers.edu/~rvaughn/install.log
A likely candidate for the
Hi Richard,
On Wed, Feb 17, 2010 at 1:41 AM, rvaug...@gmail.com wrote:
>> It would be good if we could see a copy of config.log.
>
> Install.log is over 25K lines, too large for posting.
> See it here: http://www.physics.rutgers.edu/~rvaughn/install.log
A likely candidate for the build failure i
> It would be good if we could see a copy of config.log.
Install.log is over 25K lines, too large for posting.
See it here: http://www.physics.rutgers.edu/~rvaughn/install.log
-Richard
Following is
On Feb 16, 1:29 am, David Kirkby wrote:
> On 15 February 2010 18:51, William Stein wrote:
>
>
>
On Mon, Feb 15, 2010 at 10:25 PM, rvaug...@gmail.com wrote:
> I appreciate the suggestion (I do recall a Sage v. SELinux issue),
> but after disabling SELinux and rebooting, the 'make' of
> sage-4.2.1 yielded the same result.
>
I don't think you should have to reboot for the SELinux issue. You co
I appreciate the suggestion (I do recall a Sage v. SELinux issue),
but after disabling SELinux and rebooting, the 'make' of
sage-4.2.1 yielded the same result.
-Richard Vaughn
On Feb 15, 1:31 pm, Berkin Malkoc wrote:
> It may be that SELinux is preventing necessary programs from running
> (corre
When I do an 'rpm -qa' and grep for 'gcc' I receive the following:
compat-gcc-32-c++-3.2.3-47.3.x86_64
libgcc-3.4.6-11.el4_8.1.i386
gcc-gnat-3.4.6-11.el4_8.1.x86_64
gcc4-java-4.1.2-44.EL4_8.1.x86_64
gcc-c++-3.4.6-11.el4_8.1.x86_64
gcc4-c++-4.1.2-44.EL4_8.1.x86_64
libgcc-3.4.6-11.el4_8.1.x86_64
gcc
