The symbols that dlsym wants to refer to are not part of uclibc... these
are glibc specific functions. Now my toolchain does not have glibc and
has only uclibc. So i am wondering as to how these symbols are being
referred to my ncurses.
Then they are probably being referenced via the header-files.
For instance, if uclibc does not have a <sys/stat.h>, then
I would expect the compiler to "find" it under /usr/include
Use "nm" in the objects or obj_s, etc., directory to find the
objects that use those symbols.
You can see some details by making preprocessor-output files for
the corresponding sources, e.g., I see that toe.o uses the directory
function "readdir", so
cd progs
make toe.i
and I see on my machine that resolves to the "readdir64" symbol which is
used in toe.o (looking at toe.i):
# 158 "/usr/include/dirent.h" 3 4
extern struct dirent *readdir (DIR *__dirp) __asm__ ("" "readdir64")
__attribute__ ((__nonnull__ (1)));
(your configuration will be different of course)
Any pointer as to where the problem might lie.
Regards,
Sumit
----- Original Message ----
From: Thomas Dickey <address@hidden>
To: Mike Frysinger <address@hidden>
Cc: address@hidden
Sent: Sunday, 3 June, 2007 6:25:32 PM
Subject: Re: nucrses does not build with uclibc
On Sat, 2 Jun 2007, Mike Frysinger wrote:
On Saturday 02 June 2007, Sumit Kumar Jain wrote:
I am trying to build ncurses using a uclibc toolchain. I am using the
debian way of build and am using