Hello Svante, On Sat, Dec 23, 2017 at 7:41 PM, Svante Signell <svante.sign...@gmail.com> wrote: > Hello, > > These patches was submitted to Debian November 13 2017. Nothing has > happened so far, so maybe upstream would be interested to consider the > patches for next release.
I would like to have them applied in Debian package for next release, however it is taking more time than I thought, then I am going on vacations. If you are able to upload to Debian, feel free to NMU the package, otherwise, I'll try to have a look in a couple weeks. > Thanks! > > ---------- Forwarded message ---------- > From: Svante Signell <svante.sign...@gmail.com> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Bcc: > Date: Mon, 13 Nov 2017 04:31:34 +0100 > Subject: gdb: FTBFS on hurd-i386 > Source: gdb > Version: 8.0-1 > Severity: important > Tags: patch > User: debian-h...@lists.debian.org > Usertags: hurd, experimental > > Hi, > > gdb FTBFS on GNU/Hurd due to three reasons: > > - Usage of PATH_MAX in gdb/remote.c > > - Recent changes in Hurd failing the build of gdb/gnu-nat.c > > - A name clash of struct thread_info and the kernel function thread_info() > included in gdb/thread.c and gdb/python/py-record-btrace.c. > > Include paths: > 1) defs.h: #include "gdbarch.h": struct thread_info > > 2) defs.h: #include "nm.h":#include <mach.h>:#include <mach/mach_interface.h> > where the function thread_info() is defined: > > extern kern_return_t thread_info > ( > mach_port_t target_thread, > int flavor, > thread_info_t thread_info_out, > mach_msg_type_number_t *thread_info_outCnt > ); > > The attached patches fixes these issues: > gdb-PATH_MAX.patch > gnu-nat.c.patch > struct-thread_info.patch > > Thanks :) > -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.