From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68797 invoked by alias); 18 Dec 2019 19:08:33 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 68789 invoked by uid 89); 18 Dec 2019 19:08:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 18 Dec 2019 19:08:31 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:48604) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ihegP-00047E-Ei; Wed, 18 Dec 2019 14:08:29 -0500 Received: from [176.228.60.248] (port=2947 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ihegO-0003nZ-Px; Wed, 18 Dec 2019 14:08:29 -0500 Date: Wed, 18 Dec 2019 19:08:00 -0000 Message-Id: <83fthh310d.fsf@gnu.org> From: Eli Zaretskii To: Christian Biesinger CC: gdb-patches@sourceware.org In-reply-to: (message from Christian Biesinger on Wed, 18 Dec 2019 12:56:26 -0600) Subject: Re: [PATCH] Link to -lssp when available (fixes mingw build) References: <20191218181413.128412-1-cbiesinger@google.com> <83h81x323k.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00788.txt.bz2 > From: Christian Biesinger > Date: Wed, 18 Dec 2019 12:56:26 -0600 > Cc: gdb-patches > > > Is there a way to link against libssp.a statically? If so, it would > > be better to do that. Failing that, I'd recommend not to define > > _FORTIFY_SOURCE in MinGW builds, because the above annoyances IMO > > outweigh its utility. > > Looks like the way to do that would be -Wl,-Bstatic -lssp -Wl,-Bdynamic > > However, I'm not sure that all the required autoconf changes are worth > it at this point, and maybe we should just not define _FORTIFY_SOURCE > on mingw? I'll send a patch for that shortly. Thanks, I think it's a good solution for one more reason: searching the Internet for related issues suggests that Cygwin doesn't package a static libssp library, so a static link against that might be impossible for a Cygwin build of GDB. (Please take that with a grain of salt, as I don't use Cygwin and know very little about it; what I've read on the Internet might be outdated.)