From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55616 invoked by alias); 20 Feb 2017 11:22:54 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 55603 invoked by uid 89); 20 Feb 2017 11:22:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_40,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=Who, gdbsourcewareorg, U*gdb, gdb@sourceware.org X-HELO: mail-yw0-f181.google.com Received: from mail-yw0-f181.google.com (HELO mail-yw0-f181.google.com) (209.85.161.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 20 Feb 2017 11:22:52 +0000 Received: by mail-yw0-f181.google.com with SMTP id q127so10468821ywg.0 for ; Mon, 20 Feb 2017 03:22:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7zkxZSb+e6iP3MJ+KK3ZjbEOVE4P7TQyT+5DhvxzeF4=; b=bNEZ7SyF25B1WJSclgn3+eG7viek36uvoQ1Q+U41MmIjmkV92VG8DQzL1jY+c3iSGN XixGqOwl+pXDIWzqsoBZwM5UbN/Jm1NYMWa1bt028V5zqePksaAYKnxbp8MI/h0AOyhs vOe+yrNTRnKWJ2M/cH4PSzx39jAJLKpS/aWwX0z65y1XIXKQ+gmMySdSPyuXuQjPDeM1 i0bWbiRL7rWPQ8KgW7m7I7mT89Fu+wI/Ed9jnDZEUZGvaDf/Aiw2MtEDNXRHZ3xSGSSm Xps4Jr4XhiESEHOcvZybNxOIg6VTfO0QbQrpsWW0mSE+reWqjBmUib2G1bFBLgkxSoYe c9LQ== X-Gm-Message-State: AMke39kjiVME+hvEoJ7vMxSvCyHWUjJA5Sz7sW3K7dC7dcvwP3LRgxDCLZdfpNWKXMMFlw02N9gcrdfSIdkzdA== X-Received: by 10.129.122.200 with SMTP id v191mr17159959ywc.114.1487589770617; Mon, 20 Feb 2017 03:22:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.164.199 with HTTP; Mon, 20 Feb 2017 03:22:50 -0800 (PST) In-Reply-To: References: <331a72d9-050c-7cd7-adc2-78e5f1ed6f85@redhat.com> <57147db4-83c3-2a8f-0c74-0efc6a94e9f5@redhat.com> <5967c781-4f67-06f2-db34-f4cb3818d603@palves.net> <83d1em15l7.fsf@gnu.org> From: Nitish Kumar Mishra Date: Mon, 20 Feb 2017 11:22:00 -0000 Message-ID: Subject: Re: Issue with Latest GDB on AIX with GCC-6.12 To: David Edelsohn Cc: pedro@palves.net, gdb@sourceware.org, Yao Qi Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00043.txt.bz2 Hi All ! I have created a bug for this issue. The bug id is: 21187. I have created a patch for configure file in which new configure option --enable-staticlib and --disable-staticlib is implemented. By default the linking of GDB with libstdc++ and libgcc will be static. Attching the patch with the mail. On Mon, Feb 13, 2017 at 9:08 PM, Nitish Kumar Mishra wrote: > Hi David ! > >>Who built GCC 6.1 for you? Is this an IBM build or Bull Freeware? > IBM does not have GCC-6 build yet, and generally Bull's rpm breaks our > environment. I took it from perzl.org. > But now I have tested it with Bull's RPM, static linking still not > working but removing --static-libstdc++ and --static-libgcc > is working for me as well. > Now, I will run the testsuite and will paste the result once it's finished. > > I disabled the static options manually. I don't see any configure > option for disabling the static linking. I tried with one configure > option --disable-libstdcxx, but I dont think it will lead to dynamic > linking. Anyways, for me, using this option --disable-libstdcxx > was giving compilation error, saying, "ld soes not support target". > > Thanks, > Nitish > > > On Mon, Feb 13, 2017 at 8:49 PM, Eli Zaretskii wrote: >>> From: David Edelsohn >>> Date: Mon, 13 Feb 2017 10:02:35 -0500 >>> Cc: Nitish Kumar Mishra , "gdb@sourceware.org" , Yao Qi >>> >>> >> Can we disable -static-libgcc and -static-libstdc++ for AIX? >>> > >>> > Works for me. Those are added by the top level configure. They were >>> > originally added for gcc, we just inherited it. Ideally adding >>> > those would be controllable with a configure option, IMO. >>> >>> We shouldn't disable static-libgcc and static-libstdc++ for GCC. And >>> static would be better. But linking GDB dynamically could be helpful >>> as an interim work-around. >> >> Please let's not do that on MS-Windows at least. Dynamically linking >> against these two libraries has the following 2 adverse effects: >> >> . it requires any site that distributes precompiled Windows binaries >> of GDB to also distribute the full humongous tarball of GCC >> sources (because libgcc runtime exception doesn't cover dynamic >> linking against shared libraries); and >> >> . it opens the gates of the "DLL hell", since there's any number of >> libgcc and libstdc++ DLLs from different versions of GCC floating >> around on any given Windows system with GNU software, and there's >> no practical way to ensure binary compatibility between the one >> found first on PATH and a particular version of GDB one wants to >> run