Nick Bowler wrote:
> The Linux program loader expects to find a newline in the first 128
> bytes of the file (increased to 256 in recent versions), otherwise
> you will get an ENOEXEC error from execve.
My testing indicates:
The first line which specifies the interpreter and interpreter args is l
Collin Funk cited me:
> As Bruno Haible said in a Gnulib thread [1]:
>
> > "#!/usr/bin/env perl" does not work on GuixSD (where the only program
> > that has a hardcoded file name is /bin/sh; there is no /usr and no
> > /bin/env on this distro).
>
> So I don't think it would work in this case.
>
>./configure PERL='/usr/bin/env perl'
>
> and it will substitute that into the scripts for you, but the configure
> script in Automake 1.17 exits with a fatal error if it determines that
> $PERL contains spaces. We should probably make this non fatal since the
> check i
Should we open a bug for this?
No need to open a separate bug. I can change AC_MSG_ERROR to
AC_MSG_WARN, and perhaps tweak the message a little. --thanks, karl.
On 11/21/24 12:56, Nick Bowler wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On 2024-11-20 21:56, Li, Changqing via Bug reports for Automake wrote:
The failure is cause
On 11/21/24 12:56, Nick Bowler wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On 2024-11-20 21:56, Li, Changqing via Bug reports for Automake wrote:
The failure is cause
On 2024-11-20 21:56, Li, Changqing via Bug reports for Automake wrote:
> The failure is caused by the long path of the perl in aclocal.in, the
> shebang is cutted. Could we change it like following diff?
> [...]
> -#!@PERL@
> +#!/usr/bin/env perl
Hardcoding program names like this isn't reall
On 2024-11-20 23:53, Collin Funk wrote:
> "Li, Changqing" via Bug reports for Automake
> writes:
>
>> I met an issue when try to compile automake with the perl installed
>> in a very long path which larger then max length of shebang , here
>> is the reproduce steps
>
> What shell cut off the p
Hi,
"Li, Changqing" via Bug reports for Automake
writes:
> I met an issue when try to compile automake with the perl installed in a
> very long path which larger then max length of shebang , here is the
> reproduce steps
What shell cut off the path? Seems like a bug in that shell.
As Bruno
Hi, Dear Maintainers
I met an issue when try to compile automake with the perl installed in a very
long path which larger then max length of shebang , here is the reproduce steps
1.
git clone g...@github.com:autotools-mirror/automake.git; cd automake
2.
./bootstrap
3.
./configure
4.
m
10 matches
Mail list logo
