https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
--- Comment #8 from Martin Vahi <martin.vahi at softf1 dot com> ---
Thank You for the answers/replies.
As of 2022_07_30 I am not familiar with the GCC source code, nor do I know the
GCC build system, but as someone, who can do configure-make-make_install, I
have the following observations:
observation_0)
The build fails with Bash 4.3.48,
as described at the console output at
one of the attached text-files.
observation_1)
If I use Bash 5.1.0 with the GCC code changes
that are described at another attachment/txt/diff file,
then the build completes without any errors that
I would easily notice on console.
It's up to GCC developers to figure out, how things _should_ or _should_not_
be, but that's how I fixed it for myself and it would probably help others like
me, if they didn't have to re-do the text changes in the files listed at the
attached diff-file. Probably people smarter than me can figure out, which of
the changes are actually necessary or may be the smarter people, possibly You,
can come up with some different kind of code-change that just throws out the
use of Bash features that are present at the 5.1.0 and missing from the 4.3.48,
but there is the "risk" that at some point someone comes up with some code that
still uses some features that are specific to some newer version of Bash and
some people might use even older Bash versions than the 4.3.48.
The GCC code and build scripts that I used has been packaged to ~1.2GiB (~8GiB
after unpacking wrapped xz)
2022_07_24_created_GCC_bugreport_106429_optional_appendix_01_SHA256_68f6aa8ec04f4adbd31c89e35597b2dbbfce9718ec0b801c4a40ac2dd8ad1767.tar
which MIGHT be downloadable from
(Folder view.)
https://1fichier.com/dir/uiRZKGsU
(Direct link to tar-file.)
https://1fichier.com/?qe2en1n9bh6ixl6669pi
Inside the tar-file the
./demobuild/autogenerated_tmp/GCC_v_11_2_0/gcc
includes all files as they were/are right after the failed build.
Actually the use case that I described here for custom-building GCC is just one
of the 2 use-cases that I have had. Initially I wrote the
./demobuild/try_to_compile_it.bash
for building Linux kernel for the Windows Linux layer, the WSL. I know that the
way I use Git at
https://github.com/martinvahi/mmmv_notes/tree/master/mmmv_notes/usage_demos/WSL2_Microsoft_Kernel_installation_notes_t1/WSL1_2_WSL2_upgrade_option_02_hard_and_errorprone/src/GCC/mmmv_repackaging_GCC_v_11_2_0_WSL_AMD64_t1_v02.tar.xz.file_pieces
is plain horrible and that "no decent person does that", but I like to organize
projects into folders and that's how I could shove the whole GCC building
related part to my Git repository while keeping the number of files at my
repository relatively small.
Thank You for the answers/replies and thank You for reading my comment.
