Re: [Lynx-dev] lynx startup message
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 have to find who packages lynx-current on archlinux and find out what change was done to PKGBUILD file since version where this startup message did not appear since I think a regression happened that needs a revert. On Sun, 15 Apr 2018, Jude DaShiell wrote: Date: Sun, 15 Apr 2018 22:14:36 From: Jude DaShiell <jdash...@panix.com> To: lynx-dev@nongnu.org Subject: Re: [Lynx-dev] lynx startup message 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 startup message happens on the same hardware. If not, PKGBUILD in archlinux is defective. If this message is just a system burp like linux error messages that come up as the kernel goes around them and boots the system anyway that's no problem. -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 startup message happens on the same hardware. If not, PKGBUILD in archlinux is defective. If this message is just a system burp like linux error messages that come up as the kernel goes around them and boots the system anyway that's no problem. -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
> 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 opposed to the 64-bit x86 instruction set (which is what the executable is for). "uname -m" should print the architecture name your system is running under; I'm guessing you'll see "i386". I don't know whether the Athlon K8 is 64-bit capable; I'd guess not, but if so I'll further guess that you're running a 32-bit system, not a 64-bit system, and thus can't run a 64-bit binary. (You'll probably see "i386" for 32-bit and "amd64", "x86_64", or maybe "x86-64" for 64-bit.) There is some chance you'll see something else. But I am moderately confident "Athelon" is a typo for "Athlon", indicating x86 architecture, rather than a name for an ARM variant or some such. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@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@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 mention it's a 1994-vintage machine (and here I thought *I* ran old machines with a 32-bit Celeron laptop from 2001 on my desk; 1994 is downright amazing!), I'm nigh positive Mirabilos hit the nail on the head and that you're trying to run a 64-bit executable on a 32-bit processor. If your processor (or OS) is 32-bit, the 64-bit executable won't work for you so you'll need to get a 32-bit build. -tim ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
His system, not her system. On Sun, 15 Apr 2018, Thorsten Glaser wrote: Date: Sun, 15 Apr 2018 19:27:24 From: Thorsten Glaser <t...@mirbsd.de> To: Paul Gilmartin <paulgboul...@aim.com> 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() 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 -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
On Sun, 15 Apr 2018, Paul Gilmartin wrote: Date: Sun, 15 Apr 2018 18:11:40 From: Paul Gilmartin <paulgboul...@aim.com> To: lynx-dev listserv <lynx-dev@nongnu.org> 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 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/Linux 3.2.0, BuildID[sha1]=5e21e28486e33341613cecfe484143b263c95040, stripped The other application I have on the system that uses lynx heavily is surfraw but how surfraw can be running a shell script in run instances described above I do not know. The hardware is an amd K8 Athelon built back I think in 1994. Also, What does "ls -l /usr/bin/lynx" say? What does "uname -a" say? Is it possible the message is coming from a system() call within lynx? On Sun, 15 Apr 2018, David Woolley wrote: Date: Sun, 15 Apr 2018 05:43:35 From: David Woolley 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. This message isn't coming from Lynx. It is coming from a shell script. -- gil [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 ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 <t...@mirbsd.de> To: Jude DaShiell <jdash...@panix.com> Cc: David Woolley <for...@david-woolley.me.uk>, lynx-dev@nongnu.org Subject: Re: [Lynx-dev] lynx startup message 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 proper architecture. bye, //mirabilos -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
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 > 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/Linux > 3.2.0, BuildID[sha1]=5e21e28486e33341613cecfe484143b263c95040, stripped > > The other application I have on the system that uses lynx heavily is surfraw > but how surfraw can be running a shell script in run instances described > above I do not know. The hardware is an amd K8 Athelon built back I think in > 1994. > Also, What does "ls -l /usr/bin/lynx" say? What does "uname -a" say? Is it possible the message is coming from a system() call within lynx? > On Sun, 15 Apr 2018, David Woolley wrote: > >> Date: Sun, 15 Apr 2018 05:43:35 >> From: David Woolley >>> 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. >> >> This message isn't coming from Lynx. It is coming from a shell script. -- gil ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 proper architecture. bye, //mirabilos -- Stéphane, I actually don’t block Googlemail, they’re just too utterly stupid to successfully deliver to me (or anyone else using Greylisting and not whitelisting their ranges). Same for a few other providers such as Hotmail. Some spammers (Yahoo) I do block. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 2018, David Woolley wrote: Date: Sun, 15 Apr 2018 08:54:33 From: David Woolley <for...@david-woolley.me.uk> To: lynx-dev@nongnu.org Subject: Re: [Lynx-dev] lynx startup message 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 it with /bin/sh if it doesn't start with a known prefix. All recognized binary formats have unique prefixes, and a prefix of "#!" indicates that a named interpreter, rather than the shell, is to be run. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 it with /bin/sh if it doesn't start with a known prefix. All recognized binary formats have unique prefixes, and a prefix of "#!" indicates that a named interpreter, rather than the shell, is to be run. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 <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 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 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@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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 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 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@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
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 >> 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 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 HTMLmo...@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@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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/Linux 3.2.0, BuildID[sha1]=5e21e28486e33341613cecfe484143b263c95040, stripped The other application I have on the system that uses lynx heavily is surfraw but how surfraw can be running a shell script in run instances described above I do not know. The hardware is an amd K8 Athelon built back I think in 1994. On Sun, 15 Apr 2018, David Woolley wrote: Date: Sun, 15 Apr 2018 05:43:35 From: David Woolley <for...@david-woolley.me.uk> To: lynx-dev@nongnu.org Subject: Re: [Lynx-dev] lynx startup message 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. This message isn't coming from Lynx. It is coming from a shell script. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] lynx startup message
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. This message isn't coming from Lynx. It is coming from a shell script. ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
[Lynx-dev] lynx startup message
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. -- ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
