There are several versions of DJGPP port of GCC on ftp://ftp.delorie.com/pub/djgpp/current/v2gnu.there into std::experimental::filesystem namespace. libstdcfs.a was correct in latest build. Use of std::filesytem does not work as required object files are missing fromlibrary.
There is also serious problem with libstdc++ in all off them except gpp346b.zip:
- std::tolower() and std::toupper() are badly broken
Additionally for newer versions std::filesystem support (and some other C++17 related stuff) is incorrectly not included in libstdc++. There is also libstdc++fs (libstdcfs.a for DJGPP to be distinguisahable on SFN systems) and filsystem support goes
- which GCC versions are actually being used for DJGPP?
Both problems are going to be fixed in upcoming port of GCC-10.1.0. The question is whether we need to keep earlier versions.their users stay silent and do not respond).
3.4.6 is going to stay. For example one can no more build DJGPP port of Emacs using any recent version. Versions from gcc-4.7.4 to gcc-9.3.0 will perhaps moved to ftp://ftp.delorie.com/pub/djgpp/deleted/v2gnu unless there are real need for them (or
Additionally we'll perhaps need refresh of DJGPP-v2.05 as it no more build with gcc-10.1 (and other recent versions). One version of changes can be found as part of djgpp-crx Arch Linux AUR package (https://aur.archlinux.org/packages/djgpp-djcrx/, filedjgpp-djcrx-gcccompat.patch <https://aur.archlinux.org/cgit/aur.git/tree/djgpp-djcrx-gcccompat.patch?h=djgpp-djcrx>). It cannot perhaps go in without changes as I did not need to support any older cross-compiler version for ArchLinux and there is already
|Location:||Huddersfield, West Yorkshire, UK|
|Nodes:||16 (0 / 16)|