• Re: ls returned 1 exit status

    From disloops@1:103/705 to alt.bbs.synchronet on Thursday, August 05, 2021 15:30:38
    From Newsgroup: alt.bbs.synchronet

    On Tuesday, July 6, 2021 at 5:50:03 PM UTC-4, Daniel wrote:
    Daniel <m...@sci.fi.dan.com> writes:

    "Digital Man" <digit...@vert.synchro.net.remove-cgk-this> writes:

    To: Daniel
    Re: Re: ls returned 1 exit status
    By: Daniel to alt.bbs.synchronet on Thu Jul 01 2021 04:41 am

    Check out https://sourceforge.net/p/syncterm/tickets/

    I think this problem has been reported before. Perhaps there's a solution reported there.

    Hey Digitalman,

    Thanks for the reply. I went through the open and closed tickets. The
    only one that seems to be a similar issue was deemed BS. Will you
    specify which ticket it is?
    Nevermind, I was able to fix the old installation. I'm back to working again. Thanks for your help anyway.
    --
    Daniel
    Visit me at: gopher://gcpp.world

    Hello all,

    There is not currently a Sourceforge ticket with a solution to this problem. I am experiencing the same issue that Daniel described. My problem is occurring after trying to build from source on an instance of Amazon Linux 2, which is based on RHEL.

    I can post more output here if necessary. Any help would be appreciated!

    Thanks,
    @disloops
    --- Synchronet 3.19a-Win32 NewsLink 1.113
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to disloops on Thursday, August 05, 2021 17:36:08
    Re: Re: ls returned 1 exit status
    By: disloops to alt.bbs.synchronet on Thu Aug 05 2021 03:30 pm

    From Newsgroup: alt.bbs.synchronet

    On Tuesday, July 6, 2021 at 5:50:03 PM UTC-4, Daniel wrote:
    Daniel <m...@sci.fi.dan.com> writes:

    "Digital Man" <digit...@vert.synchro.net.remove-cgk-this> writes:

    To: Daniel
    Re: Re: ls returned 1 exit status
    By: Daniel to alt.bbs.synchronet on Thu Jul 01 2021 04:41 am

    Check out https://sourceforge.net/p/syncterm/tickets/

    I think this problem has been reported before. Perhaps there's a solution reported there.

    Hey Digitalman,

    Thanks for the reply. I went through the open and closed tickets. The only one that seems to be a similar issue was deemed BS. Will you specify which ticket it is?
    Nevermind, I was able to fix the old installation. I'm back to working again. Thanks for your help anyway.
    --
    Daniel
    Visit me at: gopher://gcpp.world

    Hello all,

    There is not currently a Sourceforge ticket with a solution to this problem. I am experiencing the same issue that Daniel described. My problem is occurring after trying to build from source on an instance of Amazon Linux 2, which is based on RHEL.

    I can post more output here if necessary. Any help would be appreciated!

    My guess is that it has to do with one of the external dependencies (e.g. ncurses or maybe SDL2). Perhaps see if you update one or both of those development packages on your Linux system to something newer or the latest.
    --
    digital man

    Synchronet "Real Fact" #93:
    Synchronet v3.17b was released on January 1 of 2019 (4 years after v3.16c). Norco, CA WX: 87.6øF, 43.0% humidity, 14 mph NNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From disloops@1:103/705 to alt.bbs.synchronet on Thursday, August 05, 2021 19:58:13
    From Newsgroup: alt.bbs.synchronet

    On Thursday, August 5, 2021 at 8:36:16 PM UTC-4, Digital Man wrote:
    To: disloops
    Re: Re: ls returned 1 exit status
    By: disloops to alt.bbs.synchronet on Thu Aug 05 2021 03:30 pm

    From Newsgroup: alt.bbs.synchronet

    On Tuesday, July 6, 2021 at 5:50:03 PM UTC-4, Daniel wrote:
    Daniel <m...@sci.fi.dan.com> writes:

    "Digital Man" <digit...@vert.synchro.net.remove-cgk-this> writes:

    To: Daniel
    Re: Re: ls returned 1 exit status
    By: Daniel to alt.bbs.synchronet on Thu Jul 01 2021 04:41 am

    Check out https://sourceforge.net/p/syncterm/tickets/

    I think this problem has been reported before. Perhaps there's a solution reported there.

    Hey Digitalman,

    Thanks for the reply. I went through the open and closed tickets. The only one that seems to be a similar issue was deemed BS. Will you specify which ticket it is?
    Nevermind, I was able to fix the old installation. I'm back to working again. Thanks for your help anyway.
    --
    Daniel
    Visit me at: gopher://gcpp.world

    Hello all,

    There is not currently a Sourceforge ticket with a solution to this problem.
    I am experiencing the same issue that Daniel described. My problem is occurring after trying to build from source on an instance of Amazon Linux 2, which is based on RHEL.

    I can post more output here if necessary. Any help would be appreciated!
    My guess is that it has to do with one of the external dependencies (e.g. ncurses or maybe SDL2). Perhaps see if you update one or both of those development packages on your Linux system to something newer or the latest.
    --
    digital man

    Synchronet "Real Fact" #93:
    Synchronet v3.17b was released on January 1 of 2019 (4 years after v3.16c). Norco, CA WX: 87.6øF, 43.0% humidity, 14 mph NNW wind, 0.00 inches rain/24hrs
    --- Synchronet 3.19a-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    That is absolutely correct. I did not install SDL2 prior to attempting to compile SyncTerm. The following package installations were necessary:
    $ sudo yum install gcc
    $ sudo yum install patch
    $ sudo yum install ncurses-devel
    $ sudo yum install SDL2-devel
    Everything works now - thanks!
    --- Synchronet 3.19a-Win32 NewsLink 1.113
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)