From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from webmail.look.ca (webmail.look.ca [208.65.246.140]) by sourceware.org (Postfix) with ESMTPS id 10CF63858C5F for ; Wed, 21 Feb 2024 00:15:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 10CF63858C5F Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=idirect.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=idirect.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 10CF63858C5F Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=208.65.246.140 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708474559; cv=none; b=fdplXzLfflG40kJZ4WzVPPQP3THqrAOgRFKhkBltzJkfl+oLHLeYZU0bt8E6yGgU+Mdym8MdB6/UwxTym8aNmwylaa0dnFnSLP2iignKo1UzFwOn9Xw/3HkuwIZeeBV3bZKFl0+5GPUOLfkBLAOoM+XPn7UboVzIL9WGtv/GojE= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708474559; c=relaxed/simple; bh=QAajiYbvwQVnTKFeWrJ9e4XTtlOTm3ThtJgb2EUCI4s=; h=Message-ID:Date:Subject:From:To:MIME-Version; b=mTmvnYN6mdPVNmEzj7uaBPbgfq+x6mH7MzAYAEtZkXQwqmQ+VGWK9hYQ/AQd3Egeq/s2e91T23A7rS9T2kuOJNjUZM5kzxLQ6bIMLuvxFjKqGA3kfa45ET9xz6epdXdSVHJ+4m+en8foBZq3yf0r1sjTkb51+DO4/SlJKJ/Kbpw= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from mx4.look.ca (localhost [127.0.0.1]) by webmail.look.ca (Postfix) with ESMTP id 76586325FB8 for ; Tue, 20 Feb 2024 18:31:39 -0500 (EST) Received: from webmail.look.ca ([127.0.0.1]) by mx4.look.ca (mx4.look.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bf2PGMrb8DJP; Tue, 20 Feb 2024 18:31:38 -0500 (EST) Received: by webmail.look.ca (Postfix, from userid 33) id BDB08325FBE; Tue, 20 Feb 2024 18:31:38 -0500 (EST) Received: from 129.222.141.65 (user gemesys@idirect.com) by webmail.look.ca with HTTP; Tue, 20 Feb 2024 18:31:38 -0500 (EST) Message-ID: <564fd9196fb695e046c448024ac5f10c@webmail.look.ca> Date: Tue, 20 Feb 2024 18:31:38 -0500 (EST) Subject: GCC build from source. Where does a build of GCC, put the "gcc" executable??? From: gemesys@idirect.com To: gcc-help@gcc.gnu.org Cc: gemesys@idirect.com User-Agent: Look Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi; For various reasons, I needed to build a GCC 4.8.5 compiler from the source tarball. I did this, using gcc version 4.3 and looks like it worked. (any one reading, can jump to TL;DR at end...) Before I run "make install", I just want to run the just-made "gcc" executable file, with "./gcc --version" just to confirm the darn thing actually got built successfully and might actually work. I built in the "gcc-4.8.5" source directory. Why? Because this worked on two other vintage 32-bit machines. The build has completed - I have several "xxx-i686-pc-linux-gnu" directories, and numerous object library directories, and several sub-dirs called "gcc" - some of which have .c code, and some of which contain object files - but none of these actually have THE NEEDED GCC EXECUTABLE FILE! This is hilarious. Doing this exercise is like an old game of "Dungeons and Dragons" ("You are in a dark place, with many dark, twisty dimly-lit possible passages...") I have read the documenation on BUilding GCC from Source, and that is how I got it all to work. Now - please: Where oh where does this GCC build put the gosh-darn "gcc" program and the other related executable files? (g++, F95, etc.) In /home/gcc/gcc-4.8.5/host-i686-pc-linux-gnu/gcc I have F951, and files which appears to runable, and I have two things called: "xgcc" and "xg++" which maybe are gcc and g++ after the "make install" is run? I had to build with the curious triple-check bootstrap thing disabled, since I was running out of disk space (also hilarious). But the "make -disable-bootstrap" ran successfully to completion. I just want to inspect the built "gcc" program, confirm it is the correct new one, and actually works, before I run the "make install" to fling everything into "/usr/local...", as per CentOS/Fedora/Redhat style Linux. So - what is the secret? Does "xgcc" and "xg++" magically turn into "gcc" and "g++" and find their way into /usr/local/bin (as per Redhat Linux typical installs)? Does "GCC Build from Source" not actually create a "gcc"? I suspect this is the simple answer - but after a silly amount of google-time-waste and read/read/read of documents - I remain in the dark. :( - Mark Langdon, Proprietor, Lorcalon Farm (where we BUILD our own TOOLS!) and Owner, GEMESYS Ltd. PS and TL;DR (After more detailed examination of things, I am guessing that it is the "make install" step that creates the "gcc" in /usr/local/bin. Is that correct?) Thanx for any info, anyone might want to fling my way! -M