Re: performous FTBFS, it needs code to find the own executable

2019-07-29 Thread Samuel Thibault
Hello, Guillem Jover, le lun. 29 juil. 2019 18:32:11 +0200, a ecrit: > On Mon, 2019-07-29 at 17:06:34 +0200, Thorsten Glaser wrote: > > ① Is one of the two right for Hurd, and if so, which, > > or is different code needed, and if so, which? > > (They hardcode 1024 for path length > > but

Re: performous FTBFS, it needs code to find the own executable

2019-07-29 Thread Guillem Jover
Hi! On Mon, 2019-07-29 at 17:06:34 +0200, Thorsten Glaser wrote: > It basically does this (I’m ignoring the boring stuff like Windows): > > #if (BOOST_OS_BSD) > int mib[4]; > mib[0] = CTL_KERN; > mib[1] = KERN_PROC; > mib[2] = KERN_PROC_PATHNAME; > mib[3] = -1; >

performous FTBFS, it needs code to find the own executable

2019-07-29 Thread Thorsten Glaser
Hi, performous currently FTBFS on Hurd (and my are you people fast at figuring out the right line from the build log and letting it show up on buildd.d.o), I already fixed one issue and pushed it upstream but now there’s an OS-dependent question. It basically does this (I’m ignoring the boring st