Hi Everyone,

I send my best to those of you with family and friends that have been deeply affected by the Devastating Tsunami Waves in Asia

I have been reading thread after thread on this one and I think I know what SHOULD be the solution only it is not working!

I am attempting to ./configure imapproxy and am getting these errors:



I am running Suse 9.1 and through both YAST and downloaded RPMs I have installed:


I know that both ncurses and ncurses-dev need to be installed for the compile to work; however even though I do have them installed I still get he error.

Is this a problem with Suse 9.1 or are there additional packages that must be installed? If you can't answer the previous question, then do you know how to get around this?

In almost all of the 100 or so threads that I read previously to posting this the advice was to install one or another or both the ncurses and ncurses-dev; however I was not able to find someone else that had both installed an reported this and had a fix.

Your help and time is greatly appreciated.

ServerStorm

First, try a 'make distclean' in your imapproxy source directory.

Next, as the root user, run 'ldconfig' again just to make sure the systems knows where to find the libraries.

Then try 'locate ncurses' to see where SuSE installed it and the devel libraries.

Try ./configure --help to see if there is a default location used for the libraries, and how to set the correct path to find them.

Run ./configure (with options if required to point to ncurses)

As Suggested I First tried to run a make distclean. It gave an error:

Then I ran 'ldconfig' which proceed fine.

When I located ncurses this is a summary of the files found (minus documentation).

file:/var/lib/YaST2/you/installed/ncurses-51347
file:/var/lib/YaST2/you/mnt/i386/update/9.1/patches/ncurses-51347
file:/var/adm/YaST/InstSrcManager/IS_CACHE_0x00000001/MEDIA/suse/i586/ncurses-devel-5.4-59.i586.rpm
file:/var/lib/YaST2/you/mnt/i386/update/9.1/rpm/i586/ncurses-devel-5.4-61.3.i586.patch.rpm
file:/usr/share/man/man3/ncurses.3ncurses.gz
file:/usr/share/susehelp/meta/Administration/System/ncurses.desktop
file:/usr/include/ncurses.h
file:/usr/lib/perl5/vendor_perl/5.8.3/i586-linux-thread-multi/ncurses.ph
file:/usr/lib/zinf/plugins/ncurses.ui
file:/usr/include/ncurses_dll.h
file:/usr/lib/perl5/vendor_perl/5.8.3/i586-linux-thread-multi/ncurses_dll.ph

I have highlighted lines in Red as the paths to the files that I think it needs. I am not sure if these are correct?

Here is my botched attempts at using the options. It is quite apparent that I don't understand how to use this command properly!

I don't know if I:

a) performed the make distclean properly, but I can tell you that I was in the source directory when I issued the 'make distclean' at the command line.

b) If the file paths (highlighted in red) are what I should be including

c) how to add the paths to the options in ./configure

I have performed a few source compilations before but they were pretty vanilla - follow cut and paste scripts and I didn't have to do anything fancy what you have asked is new too me.

Thanks for your post and I hope that you might clear up some of the difficulties that I am experiencing.

Truly,
ServerStorm.

Don't worry about the CPP flags unless you're having serious compiler issues.

how about 'locate libncurses' - what does that tell you?

Hi Mcleodnine

When I type locate libncurses into the command prompt I get the following error:

Not having much luck with the old line commands today

Truly,
ServerStorm

Ahhh, yeah. Good ole SuSE....

Fire up YaST and tell it you want to install packages, search for 'locate' and install the recommendations. 'locate' and 'slocate are some very handy tools and really should be a part of the default installation of any distribution. Lightweight, zero calories, and low in satutated fats.

Installed locate (thanks for the heads-up!)

ran the command with success and what is interesting is that it did not locate ncurses:

In an earlier post in this thread using Find I was able to locate a certain number of curses files; however with 'locate libncurses' or 'locate [-d] libncurses it found nothing. Does this indicate that even though ncurses and ncursed-deve are installed that they are not located in the proper spot or listed in a environmental variable or text file?

Thanks for you help thus far. I hoping to get through it so that I can get my mail server up and running (for my new business) yikes so much to learn and so little time. Your time is Very Much appreciated!

Truly,
ServerStorm

As user 'root' - run 'updatedb'. This will make an index of all the files on your system. Most distros are setup to run this daily via a cron job.

If you want to stick with the find command try 'find / -iname "libncurses*" '

A little success

I first tried locate (as seen below) but nothing (I think because it seems to be searching /var/lib/locatedb only) so I then used find and this is what it came up with:

foozle:~ # locate libncurses
locate: /var/lib/locatedb: No such file or directory

foozle:~ # find / -iname "libncurses*"
/lib/libncurses.so.5
/lib/libncurses.so.5.4
/usr/lib/libncurses.so.1.9.7a
/usr/lib/libncurses++w.a
/usr/lib/libncurses.so.4
/usr/lib/libncurses.so.2.1
/usr/lib/libncurses.so.4.2
/usr/lib/libncurses++.a
/usr/lib/libncursesw.so.5
/usr/lib/libncursesw.so
/usr/lib/libncurses.so
/usr/lib/libncursesw.so.5.4
/usr/lib/libncurses.a

I also ran updatedb, which ran correctly - I will be looking at (in my own time) setting up Cron to do this as a daily job; although a topic for another day...

I also noticed something in Yast that may be of interest. Even though NCurses and NCurses-Deve were showing as installed when I checked the dependancies there were conflicts. I straightened out the conflicts by ensuring the version were all that what was recommended and then ncurses reported no conflicts.

Excitedly I tried ./configure again and got the same errors, but at least I feel like steps forward have been made in that we found the libncurses now, what to do with the info that the found livncurses provides?

Thanks for your continued help! I feel that we are close!

Truly,
ServerStorm

Strange.

try 'make clean' in the source directory and if that doesn't work, delete the source dir and unpack the tarball again to get a fresh start.

Now that you've run updatedb, the locate command should function properly for you. I'm pretty sure that SuSE runs updatedb every day as part of its cron jobs, so there's nothing you should have to do in that department. 'locate' is a lot faster than find as it just looks in its own database, rather than searching the entire filesystem.

Well after a wild goose chase - something that I did adversly affected x-windows on reboot and so I had to get that back up and running (which I did), I did as suggested and started from a fresh .tar file. long story short after getting down to ./configure I got the same checking for initscr in -lcurses...no error.

Further thoughts?

BTW locate did work and output the same as find only as you suggested a whole pile faster!

Thank you,
ServerStorm

some programs look for curses (not ncurses) which is what it looks like the one your having problems with is doing. so (as root):

ln -s /lib/libncurses.so.5 /lib/libcurses.so
ln -s /lib/libncurses.so.5 /usr/lib/libcurses.so

should take care of that

Wooooo Whoooooooooooo!

These simple commands did it!!!!!

If I understand this correctly the ls operation lists both filenames, but only one physical file will exist. This should mean that moving forward I should not run into the problem of some programs look for curses (not ncurses)?

Thank you __J for this solution! Mcleodnine a great big thanks to you too as I learned many things from the different processes that you asked me to try!


Gratuitous Happiness

BTW I thought I would tie up a loose end - I did figure out how to add parameter to './configure'. This worked:

Thanks again!!!!!!!!!!!!!!!!!!!
ServerStorm (getting a little less stormy all the time )

yes you understand correctly. you shouldn't run into too many programs that will require this but there are some out there.