I'm running bash and will try running lynx using bash and sh and see what messages come back. I can also check slint and debian to find out if this is specific to archlinux and if so, probably the archlinux packages were built incorrectly.

On Sun, 15 Apr 2018, Mouse wrote:

Date: Sun, 15 Apr 2018 06:48:51
From: Mouse <mo...@rodents-montreal.org>
To: lynx-dev@nongnu.org
Subject: Re: [Lynx-dev] lynx startup message

 sh: line 0: test: .: binary operator expected
This message isn't coming from Lynx.  It is coming from a shell

I think more likely it's coming from the lynx binary being mistaken for
a shell script.  Do you get the same (or a similar) message from
running "sh /usr/bin/lynx"?

The real question, of course, is _why_ it would be mistaken for a shell
script, since (at least if file(1) is to be trusted) it is not one.

That I can do no more than take guesses at, but here are two:

- It's lost its execute permission and the shell in use is guessing it
  might be a script when exec() fails, without noticing the lack of an
  execute bit.

- /lib64/ld-linux-x86-64.so.2 isn't what it's expected to be, so exec
  is failing.  (This could be because it's been damaged or because the
  binary was linked on a different system from the execution system,
  with the dynamic linker "interpreter" at a different path.)

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
X  Against HTML         mo...@rodents-montreal.org
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Lynx-dev mailing list


Lynx-dev mailing list

Reply via email to