From mint-bounce@lists.fishpool.fi Sun Apr 27 05:15:41 2008 Message-ID: <481443B0.6020700@freesbee.fr> Date: Sun, 27 Apr 2008 11:13:20 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: mint Subject: Re: [MiNT] mintlib release References: <1209150190.9724.530.camel@jetpack.demon.co.uk> <1209286120.9724.557.camel@jetpack.demon.co.uk> In-Reply-To: <1209286120.9724.557.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id m3R9FfTV001594 Alan Hourihane wrote: >> - regarding libsocket into libc integration: I think it's a good idea >> to keep a symbolic link from libsocket.a to libc.a for a while. >> Any suggestions or comments about this? > > No. I don't think this is necessary as it will find all symbols in libc > anyway. Unfortunately, if libsocket.a does not exist (even useless), an existing gcc command line using -lsocket will fail: ld: cannot find -lsocket -- Vincent Rivière