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

[Tim Mooney]

In regard to: Re: unresolved symbols with ncurses-5.6 on Alpha OSF1 5.1A,...:

> Thomas Dickey wrote:
> > On Tue, 17 Apr 2007, Martin MOKREJ wrote:
> >
> > > So, my problem is that static libs are being built on my system, but linker 
> > > is instructed to use shared libs.
> >
> > It's been a while since I encountered _that_.  The workaround (not 
> > implemented in ncurses) is to add linker directives (which of course depend 
> > on the system and compiler) such as -static and -dynamic before/after the 
> > -lncurses
>
> $ gcc ../objects/tic.o ../objects/dump_entry.o -L../lib -static -lncurses 
> -dynamic -I../progs -I. -DHAVE_CONFIG_H -I. -I../include  -D_OSF_SOURCE 
> -DNDEBUG -I/usr/home3/mmokrejs/include/ncurses -O2 -o tic
> $ 
> You are right, that works, but still imagine I would have static and dynamic
> libs site-wide installed and that the generated Makefile does not force
> the build process to use specifically the newly generated library in source
> tree:

What happens if you get rid of the -static and -dynamic directives you
added, and just add

        -oldstyle_liblookup

to LDFLAGS?  Does that fix the issue?

Tim
--
Tim Mooney                              address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164