On Fri, Jun 12, 2009 at 11:46:01PM +0100, Dr. David Kirkby wrote: > > I spoke to a Solaris linker engineer, and we both suspect that: a) > > you're using gld, > > Yes, I am. > > GNU ld version 2.15 > > [...] > > I can try it with Solaris ld.
OK, let us know how that goes. Also, if there's any bug in either autoconf or SQLite3 that is causing -lpthread to be added, that'd be worth knowing about too. I can't quite tell where that's coming from... > > Also, you say that GNU binutils are easier to use... we'd love to find > > out in what specific ways. If there's something about the Solaris ld > > that you dislike, it might be a bug that we'd gladly fix, but if you > > don't tell us, we might not learn about it. You should post about such > > things on tools-link...@opensolaris.org (even if you're working on S10). > > I'm no fan of GNU utilities - I'd love to use the Solaris tools. Sun > Studio 12 would be faster than gcc on SPARC. This is getting OT for this list, so we should take it off-list. There may be some useful information below for the list, so I'll post this. Yesterday I saw a post on blogs.sun.com about Sun Studio besting GCC on x86/64 too. GCC has lots of C extensions that Sun Studio doesn't yet (it has support for some, but not all of them), and from what you say about Sage it wouldn't surprise me if some parts of Sage used these extensions. The key thing though is this: you can mix objects compiled from C source by GCC and Sun Studio. So you can build SQLite3 with Sun Studio and Sage with GCC, if that's what you want. > There are various reports of gcc working better with the GNU linker than > the Sun one. So currently the plan is to get Sage working on 32-bit with > gcc. Next stage will be 64-bit. Whether it will ever use the Sun tools > is another matter - I think the effort in fixing so many GNUisms would > be too great. I've used GCC plenty, but on Solaris I always use the Solaris ld, and I avoid libtool like the plague. I'm tempted to contribute a Makefile.solaris for SQLite3 so as to avoid libtool and make use of Solaris linker features like -Bdirect. > I don't know if you work for Sun, but if you do, it would be really good > if Sun made some open-access Suns available for developers to test their > code, like HP do. OpenSolaris has been getting lots of FOSS integrated, and there's a /contrib repository that developers can contribute to. I'll pass the word about Sage on to the teams that are working on this. > I believe the Sun linker has been tried, but has caused more problems > than the GNU one with the other packages. That's not a fault of Sun, but > it is a fact of life. Perhaps, but we'd like to know why so we can make our linker better. Also, if gld is choking on filters, then it may be a good idea to file a bug against gld, and to at least document the incompatibility and any workarounds. On the other side, if our ld is failing because, for example, it doesn't have gld's --wrap option, or some such feature, and that becomes an issue, then we might add support for that. > I'll try removing libpthread. That should be easy enough - if all else > fails, I'll run sed on the Makefile !! :) Thanks, Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
