On Tue, 2012-01-03 at 16:11 +0100, Samuel Thibault wrote: > Svante Signell, le Tue 03 Jan 2012 15:25:09 +0100, a écrit : > > On Tue, 2012-01-03 at 14:20 +0100, Samuel Thibault wrote: > > > Svante Signell, le Tue 03 Jan 2012 11:14:16 +0100, a écrit : > > > > The problems are [...] a PATH setting issue in the Test-opts script. > > > Without adding . to the PATH the following happens: > > error in startup code > > /dev/fd/3: can't read interpreter file header > > > > when execing the program hello, in tunix.c: > > ofile = "hello"; argv = "hello"; execv(ofile, argv). > > I see. Problem is that it only cures the issue for the test. The -x > option is supposed to also work with the installed program, so I doubt > the maintainer will accept to cripple the test into accepting -x not > working without . in PATH. > > As icont passes the right things to execv(), it rather looks like an > issue in execv itself.
OK, but the .-path problems would only be for GNU/Hurd, and since there are no reports of execv problems for other architectures, then execv is broken on Hurd, and not elsewhere? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
