Re: Linking non-libtool libraries into a new backend?

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Raymond A. Ingles: "Scanner -> printer problem"
• Previous message: Graham Stoney: "Linking non-libtool libraries into a new backend?"
• Maybe in reply to: Graham Stoney: "Linking non-libtool libraries into a new backend?"
• Next in thread: Raymond A. Ingles: "Scanner -> printer problem"
• Reply: Raymond A. Ingles: "Scanner -> printer problem"
• Reply: Graham Stoney: "Re: Linking non-libtool libraries into a new backend?"

The problem is not really non-libtool libraries. The problem is
non-dll libraries, which libtool tries to handle for you. The objects
included in a shared library _must_ be compiled as position
independent code (PIC). If you don't have this, you can not link it
with a shared library.

What kind of libraries are you trying to link in?

-- 
##>  Petter Reinholdtsen <##    | pere@td.org.uit.no
 O-  <SCRIPT Language="Javascript">window.close()</SCRIPT>
http://www.hungry.com/~pere/    | Go Mozilla, go! Go!

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com





 Next message: Raymond A. Ingles: "Scanner -> printer problem"
 Previous message: Graham Stoney: "Linking non-libtool libraries into a new backend?"
 Maybe in reply to: Graham Stoney: "Linking non-libtool libraries into a new backend?"

 Next in thread: Raymond A. Ingles: "Scanner -> printer problem"
 Reply: Raymond A. Ingles: "Scanner -> printer problem"
 Reply: Graham Stoney: "Re: Linking non-libtool libraries into a new backend?"