From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by sourceware.org (Postfix) with ESMTPS id 3BEF83858D20 for ; Wed, 21 Feb 2024 00:20:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3BEF83858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 3BEF83858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::62c ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708474852; cv=none; b=anR30Ri383rZ9QKa8QmVITyGHVmPSgk9+dkiIzerdS+6sN10IWvlV8fvgKW+d7cG+0/nyvaHRrmRboufuKjeV+biRWIW27PuK+KrxbG2BhBHVYVossY2M6auvXtAeWOMaTGbdvmdDKHiHaXoZDDRLQDsaLLScYi/yJcIjOFSvA4= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1708474852; c=relaxed/simple; bh=l5Pr4VnAmg3T77Cm5J2yIFxoN8lAnOaxZDrJEhhNlRU=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=Mb/EASm29vtu02vmtWhGbefjVi3U401H26vBH0mfkq1+s+sBNmajo6jqezQyW7VvqxyzGTU8wJU+IjTjX0tEb4uEIhtNGwJlsXcv2PcPJwyTOuXZxGfTxAuK382SUDZgg03+bFAHet+ozs+ASvAXHnCX7whBRjv8pW7v/+cVVi4= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a3122b70439so748453566b.3 for ; Tue, 20 Feb 2024 16:20:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708474820; x=1709079620; darn=gcc.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5XhwjCcN1Mb1+KKBevONUyP3W/TN3t/IllWXEHsZ13c=; b=B3+fVssX4z50kSQxJwriB+LVbmt0vESRldj5QxR80WAmNgigFV7z6nGlZa6rZNrcCT k7XAs688QOmtGIOtUudIhD/xwSwmbiP0miv53C2W62m1CBSw449GBATFeqWQQwYxEzDG Uu2t0pPmv+2a88m5+pzf2sKKrVHNazY74S43XIYBDQJHC7ordyty6/7PTdR6FXDrsKb3 ccNMdUXPesCob0SLpVBKPnMyIeoUuFvSrj/Xy7KO2lfX69i7zRoFm2iJIlDVKwKeHIio VYHmnvrkXHZgvq2MQq+H3P4vU9WtwbsQRVKFApwWG4jkJiopJ1ydJI5xclTlJ58wPRXF 17Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708474820; x=1709079620; h=cc: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=5XhwjCcN1Mb1+KKBevONUyP3W/TN3t/IllWXEHsZ13c=; b=KY90UBffZnbJlM/WgkR8l8eA+FtYWfn7LRP4ahDLV02J/cOf4KvU1cnksZagU+3dmK a30/S7agOs32VuFjq/FCtd9yN/dxXui8CZCiMLmikeOveXnR+2pVmYS19HUFuhiVr02+ 5uu8f4B3TxXc5jJ/q6nFdfVLYAYS8H/qJkrvni3amjbRGldO95TVxnpx7El3IjNqxS6U Ypnke9r5A3n1miw2LScds5FJ9bMi6YivJ0PvBOIiNS8lHmdRyKuy95WwdmGRh3n2XuUH ld1HijGDgwqy2InJunwZkEbmmFfSEw9sKcINM5yF2K3u1mJHUO5/26I9c2Dbqarn4nME v/Hw== X-Gm-Message-State: AOJu0YwiV0mlNcA0v0isrRfSyFN4exsk5TbxFpZdziZkuBcw97UwHpVz JaQqghatNTnaOhgTtce+R67e8gOYI9grq96/iNZ8BeOGs6czX7mu6Ebq87sxJEjWaz0wku8drya VZfZuSMi0JRMpdMk55SopycsLK6jkJgqm X-Google-Smtp-Source: AGHT+IFYgJh1c27oXHlm34DCFCZIsIAVij/8WHC8nJbNbRxmjRZ7wBKOvJGOiloPGpPvfmGVeDmQgDzkaqPkx5J7pq8= X-Received: by 2002:a17:906:84f:b0:a3e:6aae:d342 with SMTP id f15-20020a170906084f00b00a3e6aaed342mr5915034ejd.47.1708474819517; Tue, 20 Feb 2024 16:20:19 -0800 (PST) MIME-Version: 1.0 References: <564fd9196fb695e046c448024ac5f10c@webmail.look.ca> In-Reply-To: <564fd9196fb695e046c448024ac5f10c@webmail.look.ca> From: Jonathan Wakely Date: Wed, 21 Feb 2024 00:20:08 +0000 Message-ID: Subject: Re: GCC build from source. Where does a build of GCC, put the "gcc" executable??? To: gemesys@idirect.com Cc: gcc-help@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Wed, 21 Feb 2024 at 00:18, gemesys--- via Gcc-help wrote: > > 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? Yes, they get renamed when installed. xgcc is what you're looking for. > > 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. You could always do make install DESTDIR=/some/where/else to see what would be installed. > > 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)? Not magically, just using shell commands. > > 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