From mint-bounce@lists.fishpool.fi Mon Apr 7 19:45:42 2008 Message-ID: <47FA8FF2.4080302@freesbee.fr> Date: Mon, 07 Apr 2008 23:19:46 +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] binutils 2.18 patch References: <1207174328.14588.5.camel@localhost> <47F9330F.9040603@freesbee.fr> <1207514939.14588.210.camel@localhost> <47F942CB.6070008@freesbee.fr> <1207552131.14588.213.camel@localhost> In-Reply-To: <1207552131.14588.213.camel@localhost> 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 m37Njfqs007546 Alan Hourihane wrote: >> If so, the obvious way to fix the problem would be to not use the >> --enable-shared option when building the binutils... >> I'm probably still missing something... > > No, you are not missing anything. But the patch is small and allows the > passing of --enable-shared. It follows other architectures and I don't > see any reason why it shouldn't be used. I just would like to keep the patch as small/simple as possible... When people want to compile the binutils (or GCC), they know that shared libraries are not supported, so they don't put --enable-shared on the configure command line, and everything is good. Did you face any real-wold problem without this patch ? I would like to know what other peoople think about that. -- Vincent Rivière