Hello, Marc Poulhiès, le jeu. 31 oct. 2024 14:34:50 +0100, a ecrit: > Samuel Thibault <samuel.thiba...@gnu.org> writes: > > Hello Samuel, > > > This is essentially the same as the i386-pc-gnu section, the differences > > are the same as between freebsd i386 and freebsd x86_64. > > Changes look fine. > > > +# x86_64-pc-gnu i.e. GNU Hurd > > +ifeq ($(strip $(filter-out x86_64 pc gnu,$(target_cpu) $(target_os))),) > > + > > + SELECTED_PAIRS=x86_64-gnuhurd > > + > > + LIBGNAT_TARGET_PAIRS = \ > > + a-intnam.ads<libgnarl/a-intnam__freebsd.ads \ > > I have a single question regarding this usage of the freebsd interrupt > definitions. I see it's already the case for i*86-pc-gnu, so probably > not a real issue. If those files are shared between the various freebsd > flavors and GNU Hurd, maybe we should adjust their comments and maybe > even their file names to make it explicit that GNU Hurd also depends on > them?
It could be generalized to "bsd", indeed. For such definitions, GNU/Hurd is indeed essentially a BSD-like system. Samuel > > + s-inmaop.adb<libgnarl/s-inmaop__posix.adb \ > > + s-intman.adb<libgnarl/s-intman__posix.adb \ > > + s-osinte.adb<libgnarl/s-osinte__gnu.adb \ > > + s-osinte.ads<libgnarl/s-osinte__gnu.ads \ > > + s-oslock.ads<libgnat/s-oslock__posix.ads \ > > + s-osprim.adb<libgnat/s-osprim__posix.adb \ > > + s-taprop.adb<libgnarl/s-taprop__posix.adb \ > > + s-taspri.ads<libgnarl/s-taspri__posix.ads \ > > + s-tpopsp.adb<libgnarl/s-tpopsp__posix-foreign.adb \ > > + $(ATOMICS_TARGET_PAIRS) \ > > + $(X86_64_TARGET_PAIRS) \ > > + $(GNATRTL_128BIT_PAIRS) \ > > + system.ads<libgnat/system-freebsd.ads > > Same for the system-freebsd.ads
