215 lines
4.6 KiB
HTML
215 lines
4.6 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Errors with configure or make
|
|
while trying to compile glibc</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Glibc Installation HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="Troubleshooting—if something goes wrong... "
|
|
HREF="troubleshooting.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Troubleshooting—if something goes wrong... "
|
|
HREF="troubleshooting.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Something goes wrong during make install"
|
|
HREF="something-goes-wrong-during-make-install.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Glibc Installation HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="troubleshooting.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 5. Troubleshooting—if something goes wrong...</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="something-goes-wrong-during-make-install.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="errors-with-configure-or-make-while-trying-to-compile-the-glibc"
|
|
></A
|
|
>5.1. Errors with <B
|
|
CLASS="command"
|
|
>configure</B
|
|
> or <B
|
|
CLASS="command"
|
|
>make</B
|
|
>
|
|
while trying to compile glibc</H1
|
|
><P
|
|
>Sometimes you get configuration error telling you that, for example, a
|
|
requirement is not met—typical for software or other
|
|
library-packages which are to old. I encountered this with a series of
|
|
programs, especially during the compile of all the static
|
|
software. Normally there should be no problem: get an up-to-date
|
|
version of the software or libraries needed and then compile them
|
|
according to the description found in the source tree (usually
|
|
called <TT
|
|
CLASS="filename"
|
|
>README</TT
|
|
>, <TT
|
|
CLASS="filename"
|
|
>INSTALL</TT
|
|
> or
|
|
something similar).</P
|
|
><P
|
|
>But there are sometimes cases where this just does not want to work. For
|
|
example, I experienced problems compiling a new version of my
|
|
binutils (one of the reasons why I mention them in the
|
|
requirements), as I needed to compile glibc.
|
|
In return, the configure script for the binutils told me, <SPAN
|
|
CLASS="QUOTE"
|
|
>"Your
|
|
glibc is to old!"</SPAN
|
|
> So I thought, <EM
|
|
>Here the snake starts eating
|
|
its tail</EM
|
|
>. Thankfully there is a solution for this problem: if you
|
|
can not take one big step, try taking smaller ones, but more of them.</P
|
|
><P
|
|
>In my distribution, a glibc with the version number 2.1.1 was
|
|
included. To get around the error I tried to compile version
|
|
2.1.3, which was no problem. After I installed this version of the
|
|
library, I tried to compile the binutils once more, and this time
|
|
all the requirements were met.</P
|
|
><P
|
|
>If you encounter such a <SPAN
|
|
CLASS="QUOTE"
|
|
>"loop,"</SPAN
|
|
> try to find out what
|
|
version of the software required is the minimum, then download that version
|
|
(I think that is one of the reasons why so many old versions are
|
|
still lying around on the FTP servers). After successfully
|
|
compiling and installing, try to build the software that
|
|
complained about the version again; in most cases you should now be
|
|
able to compile. It may be necessary that you continue to use this method
|
|
to compile missing or old software.
|
|
This is what I call <SPAN
|
|
CLASS="QUOTE"
|
|
>"the long tail of the rat"</SPAN
|
|
> or
|
|
<SPAN
|
|
CLASS="QUOTE"
|
|
>"domino-effect."</SPAN
|
|
> You only wanted to do one thing, but you needed
|
|
to do many more before you could make the move you wanted to. It
|
|
might be very nasty, but there is one good side to it: afterwards
|
|
you can be quite sure that many of the programs which were really
|
|
old will replaced by the time you finish your installation.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="troubleshooting.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="something-goes-wrong-during-make-install.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Troubleshooting—if something goes wrong...</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="troubleshooting.html"
|
|
ACCESSKEY="U"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Something goes wrong during <B
|
|
CLASS="command"
|
|
>make install</B
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |