Compiling module-init-tools-3.0 Failed

farmerdan · 02-29-2004, 08:28 PM

I'm preparing to migrate from kernel 2.4.22-26mdk to 2.6.3. In my reading I discovered that the module handling in the new kernel required a new modutils package. I downloaded module-init-tools-3.0--the latest stable release.

I chose to install in /sbin--simply because that's where other utilities are located in my Mandrake 9.2 distro. I ran

Code:

./configure --prefix=/   <this installs to /sbin>
make moveold  <this renames insmod, modprobe, et. all to insmod.old, modprobe.old>

Interestingly, the second step reported that this had already been done--how I did this I do not know. Then came

Code:

make
make install

I received the following error

Code:

[root@localhost module-init-tools-3.0]# make check
gcc  -g -O2 -Wunused -Wall   -o insmod.static -static insmod.o
/usr/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
make: *** [insmod.static] Error 1

I looked at config.log and everything seemed OK--if I know what I'm looking at

--config exited with exit code 0.

When I googled "/usr/bin/ld :cannot find -lc collect2: ld returned 1 exit status," there seemed to be a lot of documentation. However, none had the specific message I received. I think, based on what I read, that I need a library or devel package, but I can't decipher from the error what that would be.

If I'm on the right track, would someone point me to the library that I need. If I'm on the wrong track, I would appreciate it if someone could get me turned around.

Giovanni26 · 03-01-2004, 04:24 PM

hi
i have the same problem can you help me pleaase
many thanks

Giovanni26 · 03-02-2004, 05:27 AM

Hi,
I have resolve my problem like this:
install the glibc-static-devel
urpmi glibc-static-devel
thats all
by

farmerdan · 03-02-2004, 05:59 AM

Giovanni26, Thanks for the hint. I had just a half hour ago discovered that glibc-static-devel might solve the problem. Trying to get it now.

Will post success or failure.

Thanks again.

farmerdan · 03-02-2004, 06:42 PM

Installing glibc-static-devel did in fact solve the problem. module-init-tools-3.0 is now running happily on my PC.

I would like to pass on a couple of flags I discovered and ask two more questions.

This morning before Giovanni26 posted the solution, I googled the last line of the message I received when I ran <make check>. "make: *** [insmod.static] Error 1." The search produced nothing specific to my problem, but one of the archives caught my eye. When someone described getting this same error the response was:

Quote:

It looks like you don't have the ability to make static libraries
glibc-static-devel

This evening as I prepared to post this I looked for things that I had missed when I prepared to install this utility and in the FAQ I found

Quote:

Q) I get "/usr/bin/ld: cannot find -lc"
A) You need to install a development package which contains libc.a.

It seems like I had all the information in the FAQ to alert me to this--I like some others whose posts I have seen thought that libc.a would be a standard component in a distribution. My question is this: As I continue on my linux journey, is this something that I will encounter when installing from source or is there some documentation that alerts me to what various libraries contain and which to install?

Here is my second question. The upper level README contains installation instructions. After the step for <make install> there are three other items:

Quote:

3) If running for the first time, you might want to convert your old
modules.conf to modprobe.conf:

./generate-modprobe.conf /etc/modprobe.conf

4) If you are using devfs, copy modprobe.devfs to /etc

5) You will need to run "depmod" for your new kernel, eg:

depmod 2.5.50

I forgot about these items this morning when I completed the install; however, tonight when I "fired up" everything installed correctly and is running smoothly. I do not have /etc/modprobe.conf, and

Code:

locate modprobe.conf
locate modprobe.devfs

produces no results. I need to read the man pages for modprobe, but in the meantime, since my original goal is to migrate to kernel 2.6.3, should I anticipate any problems with this when I run <depmod> for the new kernel?

Thanks to those who answer my questions, and I hope that my experience will aid others having this same situation.