From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) by sourceware.org (Postfix) with ESMTPS id B90B73858D20 for ; Sun, 11 Jun 2023 19:04:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B90B73858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2b1a653b409so44166251fa.0 for ; Sun, 11 Jun 2023 12:04:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686510278; x=1689102278; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=n1zgh+ZXsslCCax7u0Evg63/TvUN9HnKcIatRLCHkWM=; b=ANtBlSSauhoF2jYtmtsdq18gJPKz4WuyfqP2LoIRwoQ7VaDCdofuRpRDr4Vfcokuta UxwWOcBjk+tPXQNpVAygdRjQbzbYPgbipfDKOYBMDwT26bZna3XbI3FrAmhuMkPYbxj7 5k3gA50ANQtTG8l6BHOzFA39XKZeOcqq2MPphxPMusyc++YwFUEwoIGQoGZxpkUMlOsz JQsFmoSp/vE7EXuSiixiGdqMfqi69B6nJdSmsRs7dwLWc8GXFavflwjhkobFMVLXHcmp E/VlLlUcQ9qyG6bYZz7Xv52BYk/5nXiOEWc1BQJIr9273syrd2czvwuIa4KH0KlyFxIQ kUDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686510278; x=1689102278; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=n1zgh+ZXsslCCax7u0Evg63/TvUN9HnKcIatRLCHkWM=; b=NXSXUU7xTLLcVL8z479rQq0vikZW+3cPa3o4WRDvMVx/jJhFexJ0PdP5Buz1Vuj+Xp V6cmcdYeZUckI7aiIOAJn6rH54/fiyw7FGInIK0rZKNfm5P4HBTjneRLDVydWZB0UMgM Z/PKLmXVLqnHBLz8M1ljb+Ulm7NpkW3WYPJ1PPklV4lBTYWpub/KnHaIv+3IfnUNM4Ns pNQ8iLclQMeeAiec3yCdjtOC/3UEFfzw0cS15H419C8NAoNV6/xIs6hsMTCbGdcjYxo2 4RdqJl6glHHD/5HvDjZo6hDYHnuRKxwis2BSM/FT/dWSrn/FGMYE3d1lwainLJuqT1Te mpPg== X-Gm-Message-State: AC+VfDwQ4j+d2nd0AkGQ3iBatKaRiPxkhDt9YKP0EKJRxd/h6XZysqEr YrhjJV3EEorwT6MP/NuHRbszpGWDRm7FUi6uZDfaZQe5cuI= X-Google-Smtp-Source: ACHHUZ5cJBV43dVGNothFctD8mXrJox4gzrEx2FiHZetVajD4AuAvdCwfUegAyc7VLwhs0eRtP6tesBC4z5mjgGO4oM= X-Received: by 2002:a2e:b819:0:b0:2a8:b792:d7cd with SMTP id u25-20020a2eb819000000b002a8b792d7cdmr1318015ljo.4.1686510277504; Sun, 11 Jun 2023 12:04:37 -0700 (PDT) MIME-Version: 1.0 References: <86815941-E3AC-494F-A1E8-89544D4234A6@gmail.com> In-Reply-To: From: Randy Galbraith Date: Sun, 11 Jun 2023 15:04:26 -0400 Message-ID: Subject: Re: Building gcc 4.9.2 on AIX 7.1 To: gcc-help@gcc.gnu.org Content-Type: multipart/alternative; boundary="0000000000000033e905fddf4691" X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --0000000000000033e905fddf4691 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jun 11, 2023 at 12:27=E2=80=AFPM Tom Kacvinsky via Gcc-help < gcc-help@gcc.gnu.org> wrote: > HI, > > For some reason my follow-up hasn't made it through. > > On Sun, Jun 11, 2023 at 11:27=E2=80=AFAM Tom Kacvinsky wrote: > > > > > > Those aren't binutils linker warnings. Those are coming from the system > > linker. Which probably means you are using the system assembler, too. > Or > > maybe even the odd case where you're using binutils for the assembler b= ut > > the system linker. > > > > Can you try with using binutils for the assembler and linker? I am > > assuming you either have an older version of GCC for building the newer > > version of it, or perhaps you have the Sun Pro compilers. In any case, > you > > could use whichever bootstrap compiler you have to build binutils, and > then > > put they binutils in PATH. The GCC configure script should then chose > > those for building. > > > I missed that you're on AIX. So either you're using an older version of > GCC to bootstrap, or IBM's xlc/xlC compilers to bootstrap. > > Here is a thought I had up re-thinking this. This might be an > architecture problem. Which version of the POWER chips are you using? > YOu might have to force the GCC configuration process to use -march to > specify the right processor. But as far as I know, the configure script > should be smart enough to figure that out. > > It's been about ten years since I used the xlc/xlC compilers, so I am > not sure how one would select the architecture they want. > Hi Tom. Our sys-admin team is upgrading AIX 7.1 to 7.2. This broke gcc (an issue with IBM delivering non-ansi-standard header files). So my first step is an attempt to bootstrap gcc 4.9.2 (or later) on a non-upgraded (7.1) system. This would be using our existing install of gcc. $ gcc --version gcc (GCC) 4.9.2 Here are the CPU details: $ prtconf System Model: IBM,9040-MR9 Machine Serial Number: XXXXXXX Processor Type: PowerPC_POWER9 Processor Implementation Mode: POWER 8 Processor Version: PV_8_Compat Number Of Processors: 4 Processor Clock Speed: 2850 MHz CPU Type: 64-bit Kernel Type: 64-bit LPAR Info: 12 XXXXXXXX Memory Size: 31744 MB Good Memory Size: 31744 MB Platform Firmware level: VM930_145 Firmware Version: IBM,FW930.50 (VM930_145) Console Login: enable Auto Restart: true Full Core: false NX Crypto Acceleration: Capable and Enabled Details on "ld" and "as" as per configure: $ ./configure checking build system type... powerpc-ibm-aix7.1.0.0 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking for as... as checking for dlltool... no checking for ld... ld checking for cc... cc checking for c++... c++ checking for gcc... gcc checking for as... no checking for as... as checking for ld... no checking for ld... ld checking where to find the target ar... host tool checking where to find the target as... host tool checking where to find the target cc... just compiled checking where to find the target c++... just compiled checking where to find the target c++ for libstdc++... just compiled checking where to find the target dlltool... host tool checking where to find the target gcc... just compiled checking where to find the target gcj... just compiled checking where to find the target ld... host tool And "ld" and "as" I see at the command line: $ which ld /usr/bin/ld $ file /usr/bin/ld /usr/bin/ld: symbolic link to /usr/ccs/bin/ld $ file /usr/ccs/bin/ld /usr/ccs/bin/ld: executable (RISC System/6000 V3.1) or obj module $ which as /usr/bin/as $ file /usr/bin/as /usr/bin/as: symbolic link to /usr/ccs/bin/as $ file /usr/ccs/bin/as /usr/ccs/bin/as: executable (RISC System/6000 V3.1) or obj module Because gcc 4.9.2 is broken on our AIX 7.2 I am interested (though not as a first step) in how to boostrap gcc using native C (xlc) compiler. Alas, I am still in the process of learning what options can be sent to configure to direct it to use xlc. I just saw Kai's -v suggestion. I'll try that and reply with the details. Cheers, -Randy --0000000000000033e905fddf4691--