bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Possible configure bug in glibc-2.2.3


From: Mike Kelly
Subject: Possible configure bug in glibc-2.2.3
Date: Thu, 3 Jan 2002 22:12:43 -0800
User-agent: Mutt/1.2.5i

I haven't had the time to do the actual foot work on this myself, but I ran
into an interesting problem.  I am attempting to compile glibc-2.2.3 on a
very minimal Linux system (i686), which really only has the necessary tools
available to compile glibc.

My problem is that installation fails after a successful compile.  I do not
have an install program, so configure adjusts to use the "install-sh"
program.  This shows up in config.make as "INSTALL = scripts/install-sh -c",
but this doesn't work.  The problem is that when an install is attempted
in the elf directory for example, make tries to execute
"scripts/install-sh", which doesn't exist in the elf directory, and the
whole "make install" dies.

Tracing the problem backwards to the configure script, we see that configure
knows how to do the right thing, prepending a "$(..)./" (line 1309) to the
above string, but doesn't choose that output, because of the setting of
$ac_aux_dir (line 600) (also see line 598).  At this point, I am unsure if
this is a bug in autoconf, or a bug in the configure.in template.  If you
examine the later, you will see "AC_CONFIG_AUX_DIR(scripts)" on line 6, and
I suspect that the correct fix to this would be to simply add a "./", to get
"AC_CONFIG_AUX_DIR(./scripts)".

I'm pretty sure that this would fix the problem I'm experiencing, while not
changing the functionality, and thus compatibility, of the resulting
configure script.  Unfortunately, I don't have autoconf installed, and
cannot test my theory.  Additionally, I am preparing to depart the country
in five days, and do not have the time to mess with an "autoconf side
track".

I am attempting to compile in the source directory, which, while not
recommended, is supported.  I think that this problem wouldn't exist if I
compiled in a separate source directory, but I haven't tested this.

If there are any kind souls that wish to take a look at this, I would really
appreciate it.  Chances are this bug exists in the latest version of glibc
as well, but I haven't checked.  If you have any questions about the specifics
of my configuration, please feel free to send me an email.

Thanks,

Mike
(:

-- 
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]