Re: unresolved symbols with ncurses-5.6 on Alpha OSF1 5.1A

[Thomas Dickey]

On Mon, 16 Apr 2007, Martin MOKREJŠ wrote:

> Thomas Dickey wrote:
> > On Mon, 16 Apr 2007, Martin MOKREJŠ wrote:
> >
> > > Hi Thomas,
> > > I tried to compile ncurses on some forgotten Alpha machine and I got
> > > the following:
> > >
> > > CC=cxx CXX=cxx CFLAGS="-tune ev56 -arch ev56" ./configure --prefix=$HOME
> >      ^^^ (I'd expect that to be a C++ compiler).
> >
> > That might work - at compile-time - but at configure time, lots of
> > checks would probably fail (making the #define's not reliable).
> >
> > But the errors seem more like those from problems linking a shared
> > library.  I don't see that in the command-line.
...
> Unresolved:
> cur_term
> setupterm
> tputs
> tao$ ls ../lib/libncurses
> libncurses.a    libncurses_g.a  tao$
>
>
>
> So I suspect somehow static libs are being built in my case by default.

ok.  But missing symbols sounds like either the "cxx" is building objects
that the linker isn't finding in those archives, or that "cxx" isn't
looking there.  You can see if they're defined in the archives using
"nm".  To me "cxx" means C++, so "nm -C" would (on more than one platform) 
be used to see the C++ names.  However, the __cplusplus ifdef's in the
headers are supposed to make those names all "C" rather than "C++".
If the "nm" output shows some odd names that "nm -C" fixes, that's 
possibly where the problem is.  Otherwise, check/see if the compiler can 
tell you what files it's opening.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net