OSDev.org

So I've been working on the userland for the OS I started working on last month and all has been going well, well, until I tried to compile ncurses. So, the problem I'm running into is that the configure script for ncurses seems to hang at "Checking to see if the compiler works". Unfortunately, there is nothing abnormal in the config.log. Just for testing purposes to see if I could a more useful error I edited the configure script and commented out this test. I got another hang at "Checking for ANSI headers". Again, nothing useful in the config.log. So, right now I'm trying to identify what exactly the problem is but its hard when you don't have anything to really go on. I'm assuming this has something to do with either my toolchain or a header file used in the configure tests, or... possibly automake (I kind of doubt that though, but its given me a lot of trouble in the past). So anyways, does anyone have any tips on what I should do to hopefully get a better understanding of what exactly is causing this test to hang?

Also, I know I probably didn't give enough information as my problem is rather vague, but I don't know what information would actually give information to what the problem at hand is, hence why I'm posting here. Thanks!

EDIT: Configure arguments ./ncurses-5.9/configure --prefix=/home/blablabla/install --host=i686-pc-blabla --without-tests

EDIT: So I solved the problem, I didn't realize that the configure script was not aware I was cross compiling. Running it with ./ncurses-5.9/configure --prefix=/home/blablabla/install --host=i686-pc-blabla --without-tests --build=x86_64-unknown-linux fixed my problem

A bit helpful information would be:

1) Are you cross compiling ncurses to your userland from your host?
or
2) Are you natively compiling ncurses from within the userland of your OS?

I presume it is #1 as you have



where perhaps /home/blablabla/install is your sysroot? Am I correct?

In anycase, your --host=i686-pc-blabla is probably causing configure to look for i686-pc-blabla-gcc somewhere in your path....

type

and see if something happens... if not then you need to put i686-pc-blabla-gcc in your PATH

cheers

yeah, that's my sysroot and I verified its in my path..


It can find the compiler just fine (That test in the configure script passes).

try...



Works for my cross compile test

good luck

Ha, that had nothing to do with it. I figured it out and apparently the configure script didn't know I was cross compiling and thought I was compiling on my OS. So it created an executable with my compiler and attempted to run it on linux, which apparently just hung. (I think I made my CRT0 do a JMP $ after calling the sysexit syscall). Running the ncurses configure with --build=x86_64-none-linux fixed it.