I am trying to install gcc 4.3.0 or 4.3.1 on a 64-bit CentOS 5.0 machine, fully patched, and keep getting: make[3]: *** [libgfortran.la] error 1 make[3]: Leaving directory /path/to/source/libgfortran make[2]: *** [all] error 2 make[2]: leaving directory /path/to source/libgfortran make[1]: *** [all-target-libgfortran] error 2 make[1]: leaving directory /path/to/source make: *** [all] error 2 Web searching has yielded a myriad of hits, including various bug reports. Is this a known bug with a workaround, or do I need another package to make it work, or do I need to adjust my configure line to make things happy? Thanks for any insight. Scott
On Thu, Jun 19, 2008 at 9:31 PM, Scott R. Ehrlich <scott at mit.edu> wrote:> Web searching has yielded a myriad of hits, including various bug reports. > > Is this a known bug with a workaround, or do I need another package to make > it work, or do I need to adjust my configure line to make things happy? > > Thanks for any insight.This is the second build related issue you've posted about in the last few hours. Perhaps you could share a little insight into what your end goal is here, or what you're building which requires this newer software. Traditionally this isn't the sort of thing centos is used for, so you've got my curiosity up. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
Scott R. Ehrlich wrote:> I am trying to install gcc 4.3.0 or 4.3.1 on a 64-bit CentOS 5.0 > machine, fully patched, and keep getting: > > make[3]: *** [libgfortran.la] error 1 > make[3]: Leaving directory /path/to/source/libgfortran > make[2]: *** [all] error 2 > make[2]: leaving directory /path/to source/libgfortran > make[1]: *** [all-target-libgfortran] error 2 > make[1]: leaving directory /path/to/source > make: *** [all] error 2 > > Web searching has yielded a myriad of hits, including various bug > reports. > > Is this a known bug with a workaround, or do I need another package to > make it work, or do I need to adjust my configure line to make things > happy?gcc 4.3.x isn't a centos component. centos 5 uses gcc 4.1.2 but, on a build, that first make error line should have been preceeded by some other errors from a compiler or other tool which generated the error that make is reporting.