[oi-dev] runtime linker and non-standard libraries location

Igor Kozhukhov ikozhukhov at gmail.com
Thu Jun 6 18:52:24 UTC 2013


you can move nurses libs to /usr/lib|/usr/lib/64 - and use it 

i have move it on DilOS a long time ago - works well.

no need to provide additional rules like:
LDFLAGS += -L<path> -R<path>

also i have moved headers to standard location

--
Best regards,
Igor Kozhukhov




On Jun 6, 2013, at 10:41 PM, Andrzej Szeszo wrote:

> I think I would suggest using -L/usr/gnu/lib and -R/usr/gnu/lib for
> now. If we update ncurses package we will likely provide compatibility
> links so your aspell package will carry on working.
> 
> Andrzej
> 
> On 6 June 2013 14:22, Alexander Pyhalov <alp at rsu.ru> wrote:
>> Hello.
>> I'm working on aspell port and have the following question about shared
>> libraries. In current library/ncurses the library is located in /usr/gnu/lib
>> or /usr/gnu/lib/amd64.
>> I can path -L /usr/gnu/lib/amd64 or -L /usr/gnu/lib option to ld while
>> compiling objects. But what to do with a run-time linker? Should I patch the
>> package to use -rpath linker flag or just assume that we have new ncurses?
>> 
>> Current ncurses component from Oracle provides neccessary links in /usr/lib
>> and /usr/lib/amd64.
>> --
>> Best regards,
>> Alexander Pyhalov,
>> system administrator of Computer Center of Southern Federal University
>> 
>> _______________________________________________
>> oi-dev mailing list
>> oi-dev at openindiana.org
>> http://openindiana.org/mailman/listinfo/oi-dev
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev





More information about the oi-dev mailing list