From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14090 invoked by alias); 24 Jan 2013 21:59:49 -0000 Received: (qmail 14073 invoked by uid 22791); 24 Jan 2013 21:59:48 -0000 X-SWARE-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ve0-f178.google.com (HELO mail-ve0-f178.google.com) (209.85.128.178) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 24 Jan 2013 21:59:41 +0000 Received: by mail-ve0-f178.google.com with SMTP id oz10so1763028veb.37 for ; Thu, 24 Jan 2013 13:59:41 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.52.34.176 with SMTP id a16mr3344858vdj.44.1359064781043; Thu, 24 Jan 2013 13:59:41 -0800 (PST) Received: by 10.220.23.197 with HTTP; Thu, 24 Jan 2013 13:59:40 -0800 (PST) In-Reply-To: <5100FC73.8090300@salomon.at> References: <5100FC73.8090300@salomon.at> Date: Thu, 24 Jan 2013 21:59:00 -0000 Message-ID: Subject: Re: [PATCH, regression?] Support --static-libstdc++ with native AIX ld From: David Edelsohn To: Michael Haubenwallner Cc: GCC Patches Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg01223.txt.bz2 > Ok, inside the patch file now rather than at the end of the mail text. > I'm still unsure if the patch should contain a real ChangeLog diff or > a simple comment, as I doubt the ChangeLog diff would apply smoothly. The general approach is insert the ChangeLog, as text, in the body of the email message. Create a patch for the actual changes to the source code and append it in the message if it is small or attach it if it is large. > Since switching to C++ inside gcc, it isn't possible to get working gcc/g++ > binaries installed using native ld on AIX without this patch, as these need > dynamic libstdc++.a from builddir(!). Even after successful build with the > workaround from PR55105[1], installed binaries break when removing builddir. I have added your patch, but LDFLAGS only includes -static-libstdc++ -static-libgcc for stage1, when the initial GCC does not implement it. I configure with --with-boot-ldflags=-L/usr/gnu/lib so that bootstrap will find the gmp, mpfr, mpc shared libraries. Do you have those libraries built statically or shared? Thanks, David