Flávio Cruz writes: Hello Flávio,
>> On Thu, Nov 14, 2024 at 12:44 PM <jann...@gnu.org> wrote: >> >> I'm trying to build gdb-15.2 for the 64bit Hurd using this patch >> >> <https://lists.gnu.org/archive/html/bug-hurd/2024-07/msg00001.html> [..] > I believe the problem is that you are using the C++ compiler to compile the > MiG stubs. > Have you tried to apply the following patch? > https://inbox.sourceware.org/gdb-patches/cw5yn6mfyjxdxv4kzhmqy76tjclttc3cykptidqwdfd5syrw36@r6j6p4cewhs6/T/ No, haven't seen that. Using this patch, gdb-15.2 "just builds" (TM). Phew! > I worked on it a long time ago but I remember it would prevent the > build process from having to include cstdlib. Yes, thanks! One other thing that puzzles me is that unless I explicitly configure with --enable-targets=i586-pc-gnu,x86_64-pc-gnu" (note that i586-pc-gnu _must_ be present), the [cross-]built gdb doesn't know about Hurd, it says: --8<---------------cut here---------------start------------->8--- /gnu/store/fhdw8sl6s44wvkh3v47qp5c39akcikrk-gdb-minimal-15.2/bin/gdb: warning: A handler for the OS ABI "GNU/Hurd" is not built into this configuration of GDB. Attempting to continue with the default i386 settings. --8<---------------cut here---------------end--------------->8--- As a corollary, using this GDB I found that the statically built tar segfaults on the vtrying to issue the tar: Option --mtime: Treating date '@1' as 1970-01-01 01:00:01 warning: WARN ((0, 0, _("Option %s: Treating date '%s' as %s"), p->option, p->date, treated_as)); as it looks like, on the 274 vfprintf (stderr, message, args); call. I guess I'll try replacing that with a simple fprintf for the 64bit Hurd, or comment it out altogether. Greetings, Janneke -- Janneke Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
