From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2116 invoked by alias); 21 Jun 2013 19:19:26 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 2101 invoked by uid 89); 21 Jun 2013 19:19:24 -0000 X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.1 Received: from mx72.nozonenet.com (HELO mail3.nozonenet.com) (204.14.89.25) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 21 Jun 2013 19:19:22 +0000 Received: (qmail 6188 invoked by uid 399); 21 Jun 2013 15:19:20 -0400 Received: from mail-wi0-f178.google.com (smtp@4refs.com@209.85.212.178) (de-)crypted with TLSv1: RC4-SHA [128/128] DN=unknown by mail3.nozonenet.com with ESMTPSAM; 21 Jun 2013 15:19:20 -0400 X-Sender: smtp@4refs.com Received: by mail-wi0-f178.google.com with SMTP id k10so913848wiv.5 for ; Fri, 21 Jun 2013 12:19:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=51rOUX8K+H+6B6D6TlhYGaM3UXnirGJn8ST/BCWnMO0=; b=IIC5JgvkTn2u2WL8yPe3V7y5Zv+ps8r0Vx8z90Mz8Rj4chDuMyrVOSjKuDsDOJyw43 5MIwYyoOZ1rQWf1frOzlzCfdgeLtuSrausrSBfm6Qqm5+w0CBBfWi0LkjbT16Iq2uoix n4McKt/OZuk7eIOd5sBdE1BJvNLP85Xy10X5LpDawu09ABn8hzg8re/VP5WQJxICwTwm ia0mTYlGdeiiIPabCJ//aaJiijNnPDprPGmiQp8Xd03OXxjhjhYqV4PLPGUL8RDJ8NGZ guP4Ul6rkljVnSK3yvGFjI+9F8ibnonfgJp4nFnbkZbGWr8SiMdGTjb9Lrcx9bnl1OEz ItMA== X-Received: by 10.180.91.131 with SMTP id ce3mr3645139wib.55.1371842359735; Fri, 21 Jun 2013 12:19:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.195.12.196 with HTTP; Fri, 21 Jun 2013 12:18:59 -0700 (PDT) In-Reply-To: References: From: Uri Moszkowicz Date: Fri, 21 Jun 2013 19:19:00 -0000 Message-ID: Subject: Re: Trouble building AR To: Ian Lance Taylor Cc: gcc-help Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-06/txt/msg00180.txt.bz2 Thanks for identifying it - good so I'm not crazy :) I tried your fix and I think it worked? I get this error when linking now: <.a file>: could not read symbols: Bad value collect2: error: ld returned 1 exit status I tried building the latest stable GCC, 4.8.1, and binutils, 2.23.2, but an error buildling it too: /lib64/ld-linux-x86-64.so.2: could not read symbols: Invalid operation This is on a RHEL4u8WS machine. On Wed, Jun 19, 2013 at 6:06 PM, Ian Lance Taylor wrote: > On Wed, Jun 19, 2013 at 3:04 PM, Uri Moszkowicz wrote: >> Log uploaded here: >> >> http://www.4refs.com/gcc.log >> >> It seems to be looking in the right places just not for the right >> file. It looks for "real-ld", "collect-ld", and "ld-new" but not "ld". > > This looks like a bug. It looks like it has been fixed in current > mainline. It looks like when you build with the binutils as a sibling > directory, it finds ld-new in the ld directory. Then it mistakenly > starts looking for that, rather than ld. I haven't tried but you may > be able to work around this by using the GCC configure option > --with-plugin-ld=/path/to/your/ld. > > Ian