Building libgcc and libstdc++

[djipi]

The script works pretty well, it builds the newlib but not the libgcc and libstdc++ from gcc.

[haarer]

Thanks for the Feedback!

Could you please add the Info:

• Platform you're builiding in (Linux, or msys..) please add also the distribution
• target architecture (arm, m68k,..)

There are currently some build variants lacking some parts.

[djipi]

Sure.

• Windows 10 platform (MSYS2).
• m68k.

[haarer]

I believe, this is dependent on the MSYS2 environment. It does not work currently with MSYS2 UCRT64, but it does work with MSYS2 MSYS.

[djipi]

For my understanding, to build libgcc and libstdc++ included with gcc, a couple of steps must be performed.

1. Build gcc.
2. make -j all-target-libgcc all-target-libstdc++-v3
3. make -j install-target-libgcc install-target-libstdc++-v3

[haarer]

Am 1. Mai 2024 14:32:05 MESZ schrieb Jean-Paul Mari @.***>:

For my understanding, to build libgcc and libstdc++ included with gcc, a couple of steps must be performed.

1. Build gcc.
2. make -j all-target-libgcc all-target-libstdc++-v3
3. make -j install-target-libgcc install-target-libstdc++-v3

-- Reply to this email directly or view it on GitHub: https://github.com/haarer/toolchain68k/issues/3#issuecomment-2088401035 You are receiving this because you commented.

Message ID: @.***> You're probably referring to the "two stage build", needed for Cross compiles of gcc.

The build Script does a "two stage build" for gcc, with either newlib or avrlib as intermediate step, depending on the target platform.

That is:

1. Build the cross gcc
2. Build the embedded c library using that gcc
3. Build the gcc libraries against that embedded c library. Of course every step requires proper configuring, builiding and installing...

That is the same for both build Platforms.

Are you builiding on MSYS2 in an UCRT or in an MSYS Environment?

-- Gruß, Alexander

[djipi]

I use the msys64 / MINGW "standard" environment, not UCRT64 or clang.