Error encountered for the stage 5.13. Ncurses-5.6

just.srad · 09-12-2008, 08:39 AM

While executing the following command:

Code:

./configure --prefix=/tools --with-shared \
--without-debug --without-ada --enable-overwrite

i got this error as shown below

Code:

configure: error: Cannot link with GPM library

Here is the output of the command.

Code:

lfs:/mnt/lfs/sources/ncurses-5.6$ ./configure --prefix=/tools --with-shared --without-debug --without-ada --enable-overwrite
checking for egrep... grep -E
Configuring NCURSES 5.6 ABI 5 (Fri Sep 12 09:12:01 GMT 2008)
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
Configuring for linux-gnu
checking for prefix... /tools
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking version of gcc... 4.1.2
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking whether gcc understands -c and -o together... yes
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... -DCC_HAS_PROTOS
checking for ldconfig... /sbin/ldconfig
checking if you want to ensure bool is consistent with C++... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for g++... /usr/bin/g++
checking version of g++... 4.1.2
checking if you want to build C++ binding and demo... yes
checking if you want to build with Ada95... no
checking if you want to build programs such as tic... yes
checking if you wish to install curses.h... yes
checking for mawk... no
checking for gawk... gawk
checking for egrep... (cached) grep -E
checking for a BSD compatible install... /usr/bin/install -c
checking for tdlint... no
checking for lint... no
checking for alint... no
checking whether ln -s works... yes
checking whether make sets ${MAKE}... yes
checking if filesystem supports mixed-case filenames... yes
checking for ctags... no
checking for etags... no
checking for makeflags variable...
checking for long file names... yes
checking if filesystem supports mixed-case filenames... (cached) yes
checking for ranlib... ranlib
checking for ld... ld
checking for ar... ar
checking for archiver options (symbol AR_OPTS)... rv
checking if you have specified an install-prefix...
checking if you want to build libraries with libtool... no
checking if you want to build shared libraries... yes
checking if you want to build static libraries... yes
checking if you want to build debug libraries... no
checking if you want to build profiling libraries... no
checking for specified models... shared normal
checking for default model... shared
checking if you want to build a separate terminfo library... no
checking if you want to link with the GPM mouse library... maybe
checking for gpm.h... yes
checking for Gpm_Open in -lgpm... no
configure: error: Cannot link with GPM library

Appreciate if anyone here could give some hints as to overcome this error.
Thanks.. =)

FLLinux · 09-12-2008, 09:48 AM

I have to add the option --with-gpm=no so it will configure it without that library. and everything worked fine.

just.srad · 09-12-2008, 06:30 PM

Thanks man...appreciate your help. I'll try it in the late morning.

One more question, not sure you could help to clear my doubt.

At the initial stage, we were told to create a Build directory for Binutils-2.17 - Pass 1 and GCC-4.1.2 - Pass 1.
Somehow i couldn't understand the instruction, so i just compile them in $LFS/sources and after i had done what needed
to be done, i just deleted the sources directory away and recreate again for the next package to be compiled.

So the question is, will the absence of the two build directories affect the rest of the installation of LFS?

If it does, then i think i'll redo it from scratch again.. and that will be my 4th time .

Thanks.

Justin

FLLinux · 09-12-2008, 06:50 PM

No when you run the second pass of the binutils and the glibc you will recreate the directory anyway.

What they want you to there is to create a second directory to build the tool in. so you source directory would look like

Source
----Binutils-2.17
----Binutils-build

Then when you are done compiling you can just delete the build directory and keep the 2.17 for the second pass. The way you did it shouldn't cause any trouble.

Took me a few runs through the first part of the book to get it right as well.

just.srad · 09-12-2008, 09:38 PM

okay, got it! Let me try it again later on. Will post it here again once .. i manage to get it up successfully.

Thanks FLLinux . =)

just.srad · 09-13-2008, 08:03 AM

erh... actually i had switched off my pc already.. i tried to continue from where
i stopped.. by setting up the initial environment and entered all the previous symbolic links
as stated in "5.4. GCC-4.1.2 - Pass 1" and "5.7 Adjusting the Toolchain".

I did execute the "./configure.... " with the option as suggested by you and therefore it ends without error.
However, i did encounter error when i executed the "make install".

I didn't record the error message though.

Does this mean i need to start from scratch again?

Thanks.

FLLinux · 09-13-2008, 08:50 AM

If you could post the error that would be great.

I don't think you would need to start over, just might what to check that you got all the links and directories setup correctly.

just.srad · 09-18-2008, 08:35 AM

FLLinux, thanks for your support.

Actually i re-do from scratch again, took about 2 days and just completed this afternoon.

Fast bootup.. but still can't be of any use yet...

And i need to sort out some minor issues before i could continue
with the BLFS.