From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8924 invoked by alias); 23 Feb 2010 13:13:47 -0000 Received: (qmail 8800 invoked by uid 22791); 23 Feb 2010 13:13:46 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.network-theory.co.uk (HELO mail.network-theory.co.uk) (66.199.228.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 23 Feb 2010 13:13:40 +0000 Date: Tue, 23 Feb 2010 13:13:00 -0000 Message-ID: <87zl30i0mj.wl%bjg@network-theory.co.uk> From: Brian Gough To: "Field G. Van Zee" Cc: gsl-discuss mailing list Subject: Re: Feedback from GSL folks on libflame 4.0 In-Reply-To: <4B7F656C.5040406@cs.utexas.edu> References: <4a00655d1002171047t4e87fb85w88b609245e3f9a8e@mail.gmail.com> <4B7D90B5.4020707@cs.utexas.edu> <1266537635.27033.79.camel@manticore.lanl.gov> <4B7F656C.5040406@cs.utexas.edu> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Message-Mac: de455093cf0092a141c7b5cccf2654fa Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00044.txt.bz2 At Fri, 19 Feb 2010 22:30:36 -0600, Field G. Van Zee wrote: > Or, as you said, we could go the errno route. We would need someone > else (Brian) to explain how exactly to implement this sort of thing. Using errno in a multithreaded program relies on operating system support for thread-local storage, which creates a new set of portability problems of its own. > We recently added shared library generation. We compile the source > with -fPIC and then link with -shared. Worked the first first time I > tried it, and so it seemed too good/easy to be true. Am I missing > something? It is that simple on GNU/Linux, but other operating systems have different incompatible methods. Also, there is the issue of supporting shared library versions if you want to allow the library to be safely updated independent of any applications using it. -- Brian Gough