Add gcc/gfortran packages

[waruqi]

Is your feature request related to a problem? Please describe.

• toolchain
• library

like llvm package

#5044

refer

• https://github.com/Homebrew/homebrew-core/blob/master/Formula/g/gcc.rb

Describe the solution you'd like

.

Describe alternatives you've considered

No response

Additional context

No response

[xq114]

gcc的编译挺复杂的，放在这里有个问题：比如package libabc 依赖gfortran，理论上应该先找系统gfortran，再走xmake-repo编译。但是 xmake l scripts\test.lua -vD libabc 不加 --shallow 的话会使得 ci 重新编译gcc，测试耗时拉的非常长；加 --shallow 又会让别的包也找到系统包上去，无法作完整的测试

[xq114]

libomp也有类似问题，实际使用时几乎所有人都会用发行版提供的和编译器版本匹配的预编译 libomp，但ci测试都是走的xmake-repo编译，多此一举同时还造成ci环境和实际使用不匹配 #4977

[waruqi]

但是 xmake l scripts\test.lua -vD libabc 不加 --shallow 的话会使得 ci 重新编译gcc，测试耗时拉的非常长；加 --shallow 又会让别的包也找到系统包上去，无法作完整的测试

不对吧，--shallow 只是决定是否拉取依赖， 并不决定是否走系统库。。。即使 没设置 --shallow ，拉依赖时候，也是优先找的 system 包的，找不到才会去远程拉。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Libomp also has a similar problem. In actual use, almost everyone will use the precompiled libomp provided by the distribution version that matches the compiler version. However, ci tests are all compiled with xmake-repo. This is unnecessary and also causes a mismatch between the ci environment and actual use. #4977

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

However, if xmake l scripts\test.lua -vD libabc does not add --shallow, it will cause ci to recompile gcc, and the test will take a very long time; adding --shallow will also cause other packages to find the system package, which cannot do a complete test

No, --shallow just decides whether to pull dependencies. . Even if --shallow is not set, when pulling dependencies, the system package will be searched first. If it cannot be found, it will be pulled remotely.