On 15/04/18 04:50, Jude DaShiell wrote:
sh: line 0: test: .: binary operator expected
On archlinux why does this happen with lynx and lynx-cur?
Is lynx not yet configured correctly or is this a compile error?
Is this message a warning or an error?
I'm using UTF-8 if that helps any system-wide.
When I run /usr/bin/lynx or just type lynx to run lynx at command prompt
that strange message comes up either way. Now when I run:
file /usr/bin/lynx
/usr/bin/lynx: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linu
>>> sh: line 0: test: .: binary operator expected
>> This message isn't coming from Lynx. It is coming from a shell
>> script.
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
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
running sh /usr/bin/lynx returns:
/usr/bin/sh cannot execute binary file.
On Sun, 15 Apr 2018, Mouse wrote:
Date: Sun, 15 Apr 2018 06:48:51
From: Mouse
To: lynx-dev@nongnu.org
Subject: Re: [Lynx-dev] lynx startup message
sh: line 0: test: .: binary operator expected
This message isn't comin
On 15/04/18 13:44, Jude DaShiell wrote:
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.
If it was built for the wrong architecture, it could cause problems, as
the low level code will try and run
Interesting, this is happening with bash and so far lynx is the only
program doing this. Bash did have a recent update and has quite the bug
colony some of them old enough to be called features. The timer
internal in bash is probably still not working after all of these years.
On Sun, 15 Apr
Jude DaShiell dixit:
> /usr/bin/lynx: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
^^
> I do not know. The hardware is an amd K8 Athelon built back I think in 1994.
I think perhaps you have an i386 system and are trying to run
an amd64 binary. Use lynx for the pr
On 15/04/18 20:51, Thorsten Glaser wrote:
I think perhaps you have an i386 system and are trying to run
an amd64 binary. Use lynx for the proper architecture.
I think she said she had an ARM system, although the same principle applies.
___
Lynx-dev m
On 2018-04-15, at 04:35:56, Jude DaShiell wrote:
> When I run /usr/bin/lynx or just type lynx to run lynx at command prompt that
> strange message comes up either way. Now when I run:
> file /usr/bin/lynx
> /usr/bin/lynx: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
> dynamically lin
Paul Gilmartin dixit:
>Is it possible the message is coming from a system() call within lynx?
No, it comes from the shell trying to run the lynx ELF/amd64 binary
as a shell script after the execve(2) syscall returned ENOEXEC because
her host system is ARM (IIRC).
bye,
//mirabilos
--
FWIW, I'm q
No, I have no i386 system here. The only intel stuff in this system is
some of the peripherals on the motherboard, all systems in this house
are amd.
On Sun, 15 Apr 2018, Thorsten Glaser wrote:
Date: Sun, 15 Apr 2018 15:51:13
From: Thorsten Glaser
To: Jude DaShiell
Cc: David Woolley , lynx
[jude@taf ~]$ uname -a
Linux taf 4.15.15-1-ARCH #1 SMP PREEMPT Sat Mar 31 23:59:25 UTC 2018 x86_64
GNU/Linux
ls -l /usr/bin/lynx
-rwxr-xr-x 1 root root 1872936 Apr 14 15:07 /usr/bin/lynx
On Sun, 15 Apr 2018, Paul Gilmartin wrote:
Date: Sun, 15 Apr 2018 18:11:40
From: Paul Gilmartin
To: lynx-de
On Sun, 15 Apr 2018, Paul Gilmartin wrote:
Date: Sun, 15 Apr 2018 18:11:40
From: Paul Gilmartin
To: lynx-dev listserv
Subject: Re: [Lynx-dev] lynx startup message
On 2018-04-15, at 04:35:56, Jude DaShiell wrote:
When I run /usr/bin/lynx or just type lynx to run lynx at command prompt that
His system, not her system.
On Sun, 15 Apr 2018, Thorsten Glaser wrote:
Date: Sun, 15 Apr 2018 19:27:24
From: Thorsten Glaser
To: Paul Gilmartin
Cc: lynx-dev@nongnu.org
Subject: Re: [Lynx-dev] lynx startup message
Paul Gilmartin dixit:
Is it possible the message is coming from a system() ca
On 2018-04-15 20:04, Jude DaShiell wrote:
> No, I have no i386 system here. The only intel stuff in this
> system is some of the peripherals on the motherboard, all systems
> in this house are amd.
In this case, "i386" refers to a 32-bit system and "amd64" refers to
a 64-bit system.
As you menti
> No, I have no i386 system here. The only intel stuff in this system
> is some of the peripherals on the motherboard, all systems in this
> house are amd.
Not i386 in terms of "Intel 80386 CPU", but i386 in the sense of "same
basic instruction set as Intel 80386": 32-bit x86 instruction set as
o
Tim Chase dixit:
>As you mention it's a 1994-vintage machine (and here I thought *I*
I believe that to be a mistake, as Athlon weren’t around back then.
On the other hand, I do run lynx on a Mitac 4023 machine, 80486DLC-33
with 10 MiB RAM, occasionally. (My main server is a Pentium 233 MMX
thoug
I reinstalled lynx-current on archlinux using makepkg and this startup
message has not gone away. Also, the PKGBUILD run by makepkg identifies
my system as an x86_64 system. This gets me closer to a possible
solution. I need to check debian and slint after updating both and see if
the same s
Okay, neither debian nor slint provide that lynx startup message only
archlinux. So I go back to archlinux and because I have a slow wifi
connection I run lynx on a local file and that lynx startup message
still appears which clears slow wifi connections being the cause for
this message. I'll
20 matches
Mail list logo
