From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) by sourceware.org (Postfix) with ESMTPS id 0C04B395C03C for ; Fri, 13 May 2022 23:21:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0C04B395C03C X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-5.997, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, NICE_REPLY_A -2.89, T_SCC_BODY_TEXT_LINE -0.01, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 24DNLq4i004764 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [172.16.35.2] (cpeac202e7325b3-cmac202e7325b0.cpe.net.cable.rogers.com [99.253.170.241]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 24DNLq4i004764 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 13 May 2022 19:21:54 -0400 Message-ID: Date: Fri, 13 May 2022 19:21:52 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: bootstrap fails on Debian ppc64 with fatal error: bits/libc-header-start.h: No such file or directory Content-Language: en-US To: Jonathan Wakely Cc: gcc-help References: <7f1f1a2f-6c9f-d3ad-8aa1-499c87eb8caf@blastwave.org> <05fc1487-9080-5822-4e32-81cf49d13961@blastwave.org> <91d0b89c-2001-1b2c-cbd7-d9b390c9ee8b@blastwave.org> From: Dennis Clarke In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2022 23:22:00 -0000 >>> Honestly, I find that hard to believe. >> >> Me too! >> >>> >>> One or the other is needed. If you need both, I think you're the only >>> person in the world who needs that. >>> >> >> Not bloody likely right? I am looking into that and I think the real >> issue is that the versions wanted in the source tree must be the same as >> the stuff dragging in by the script kicker download_prerequisites : >> >> https://gcc.gnu.org/install/prerequisites.html >> >> The in-tree build is only supported with the GMP version that >> download_prerequisites installs. > > Right, you should be using that script. > > https://gcc.gnu.org/wiki/InstallingGCC > Well what difference does it make anyways? The correct versions are the correct versions. > Or (as that page says) just install the debian packages and stop > installing them by hand. But I want to have the libs around as fully non-optimized and no assembly single steppable debug enabled full of goodness. Which I can certianly do. >> However what do I know? There is another page that says do a bootstrap4 >> for extra spice and flavour in your result. That doesn't fly. > > Well stop trying to do weird stuff and just Keep It Simple. > That just drains the joy out of everything. However to be really clear all I wanted was to boot strap gcc on a few machines and as usual I run into problems. Most people these days never see the sources and only get packages pre-built by someone else somewhere magic. Sort of defeats the whole reason why the source is open right? May as well just install MS Windows Vista and be happy. Also there is great learning stuff to be had in the process. Not the least of which is from good folks like Segher Boessenkool : https://gcc.gnu.org/pipermail/gcc-help/2022-May/141568.html There is a valid point there. Am I building a compiler which is already crippled? Hard to know for sure. >> >> Whoa ... hold on a sec. I generally never use the little magic script >> download_prerequisites. I had better check that : > > You should use it. It makes everything much simpler than you're making it. > Well it does the same thing and all that is left is the patch for mpfr. >> Okay so it needs 'wget'. Fine. Easy to fix that. > > It uses curl instead if wget is not found. Most people have one or the > other already installed. Yeah, I prefer curl. Regardless ... > >> Same stuff I use however the mpfr *needs* a patch. > > Eh? Why? Those folks working on gmp and mpfr really are the experts. The page says : https://www.mpfr.org/mpfr-current/#download The bugs listed below have been fixed (latest update: 2021-05-17). See https://www.mpfr.org/mpfr-current/#fixed Thirteen bug fixes and from what I have heard directly from some good folks the code in GMP has been subjected to an actual proof. The MPFR code is in process. I gather those bug fixes are valuable and trivial to apply. In fact the download_prerequisites script could be updated to fetch the patches and just apply them. > >> I must have made a mistake somewhere. >> . . . > > I would also delete the source tree and untar it again, in case you've > fouled it up somehow. And then run contrib/download_prerequisites > again. Yep. Starting over from scratch seems like a good idea on Friday the 13th. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional