OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Martin Iturbide on May 23, 2020, 09:40:07 pm

Title: DOSBox Issue - STDCPP6?
Post by: Martin Iturbide on May 23, 2020, 09:40:07 pm
Hi

I have an ArcaOS 5.0.4 VM with the updated libraries from ANPM, and today I installed DOSBox 0.74 (30 March, 2019)

I'm getting this error and it is not running.
Code: [Select]
[C:\Programs\DOSBOX]dosbox
DOSBox version SVN
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---

Killed by SIGSEGV
pid=0x00c7 ppid=0x00c4 tid=0x0001 slot=0x00db pri=0x0200 mc=0x0001 ps=0x0010
C:\PROGRAMS\DOSBOX\DOSBOX.EXE
STDCPP6 0:0001b26d
cs:eip=005b:1e24b26d      ss:esp=0053:0289fb20      ebp=0289fb38
 ds=0053      es=0053      fs=150b      gs=0000     efl=00012287
eax=0289fe2c ebx=00000000 ecx=199b5f00 edx=199b5f00 edi=0289feb8 esi=0289fb5c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

No POPUPLOG. I tried erasing all the duplicated DLLs from the DOSBox directory, and even trying SDL-1.2.15-20160303.zip runtime and I still have the same error.

Anybody experiencing a similar issue? Any ideas how to make it work?

Regards
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 23, 2020, 10:51:35 pm
I have probably the same problem here. I don't know, if that's caused by SMP or by the updated \usr\lib files. I guess, the first. I've changed on 2020-04-04 from an 15-years old system to a more recent AMD FM2+ system with 4 cores.

Since I've written the WarpIN macros for the next version, I had tried the installation on the newer system with the result that DOSBox isn't working. Unfortunately I haven't tried that before on that machine. It works well in my ArcaOS VirtualBox guest on a different system.

I haven't addressed Jochen so far and haven't heard from him since a long time.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 23, 2020, 11:22:13 pm
Here's the log from trying out my recent .wpi build with the binaries from the last released DOSBOX0.74_30.03.19.EXE. The installation works and finds no DLLs that require installation, but the first startup of dosbox.exe fails:

Code: [Select]
epm: C:\Programs\DOSBox > dosbox.exe
DOSBox version SVN
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---

Killed by SIGSEGV
pid=0x0c88 ppid=0x0c86 tid=0x0001 slot=0x009a pri=0x0200 mc=0x0001 ps=0x0010
C:\PROGRAMS\DOSBOX\DOSBOX.EXE
STDCPP6 0:0001b26d
cs:eip=005b:1c94b26d      ss:esp=0053:0289fb20      ebp=0289fb38
 ds=0053      es=0053      fs=150b      gs=0000     efl=00010287
eax=0289fe2c ebx=00000000 ecx=17bc5f00 edx=17bc5f00 edi=0289feb8 esi=0289fb5c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

epm: C:\Programs\DOSBox >
Title: Re: DOSBox Issue - STDCPP6?
Post by: Joop on May 24, 2020, 12:43:33 am
It is a long time ago that I installed DosBox, I'm not on the latest and I do now that it is important to have a right dosbox.conf. At first it did not start on my system because I didn't have this file correctly.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 24, 2020, 01:06:52 am
It is a long time ago that I installed DosBox, I'm not on the latest and I do now that it is important to have a right dosbox.conf. At first it did not start on my system because I didn't have this file correctly.
Sure, that is known. My installation creates a valid one if it doesn't exist.

Here's my README.OS2 version, see the section "Basic configuration":

Code: [Select]
_____________________________________________________________________________

   Information
_____________________________________________________________________________

   DOSBox is a DOS emulator that uses the SDL library which makes DOSBox very
   easy to port to different platforms. DOSBox has already been ported to
   many different platforms, such as Windows, BeOS, Linux, MacOS X etc.

   DOSBox also emulates CPU:286/386 realmode/protected mode, Directory
   FileSystem/XMS/EMS, Tandy/Hercules/CGA/EGA/VGA/VESA graphics, a
   SoundBlaster/Gravis Ultra Sound card for excellent sound compatibility
   with older games etc.

   You can "re-live" the good old days with the help of DOSBox, it can run
   plenty of the old classics that don't run on your new computer!

   DOSBox is totally free of charge and open source.


_____________________________________________________________________________

   License
_____________________________________________________________________________

   GNU General Public License (GPL) version 2.


_____________________________________________________________________________

   OS/2 port
_____________________________________________________________________________

   OS/2 package maintained by Jochen Schäfer.
   Icons provided by David Graser.
   Installation scripts and packaging by Andreas Schnellbacher.

   If you have problems with running DOSBOX, please contact me:
   josch (at) joschs-robotics.de


_____________________________________________________________________________

   Web sites
_____________________________________________________________________________

   DOSBox/2 for OS/2 and eCS Web Site:

      http://www.joschs-robotics.de/dosbox/

   DOSBox Official Web Site:

      http://dosbox.sourceforge.net/


_____________________________________________________________________________

   Installation
_____________________________________________________________________________

   The WarpIN installation is complex and feature-rich for maximal
   convenience. Usually a log file is created for easier error-catching.

   __________________________________________________________________________
   System DLLs

   Used system DLLs are checked for existence. On the WarpIN 'DLL detection'
   page, all DLLs and their states are listed.

   When missing system DLLs are detected, the package 'DOSBox/2 Support DLLs'
   is activated on the Packages page. Missing DLLs are then installed by a
   call to yum. That requires an RPM/YUM installation.

   This package doesn't provide the support DLLs anymore. If you didn't
   already install the DLLs, or don't use RPM/YUM, you can fetch the DLLs
   from here:

      http://rpm.netlabs.org/release/00/zip

   For maximal compatibility with other applications, please don't use
   outdated DLLs.

   __________________________________________________________________________
   Update

   The current version can be installed over an old one without
   uninstallation.

   The previously installed language package is selected automatically. Note
   that this applies only to systems where at least version 0,74.3 is
   installed.

   On updating an existing version, old files that don't stem from the
   current installation, are deleted. That applies also to system DLLs within
   the DOSBox installation directory. (Old versions provided the installation
   of all used system DLLs.)

   __________________________________________________________________________
   Language setup

   On selecting and installing a language package, the configuration file
   dosbox.conf is automatically edited. For more details, see the section
   'Basic configuration' below.

   Note that this file is copied from the eng subdirectory to the
   installation directory, if it doesn't exist.

   When multiple languages are selected, then the last one in the list wins.

   __________________________________________________________________________
   Verbosity and Configuration, Installation and Distribution (CID)

   The verbosity during installation can be controlled in three ways: Logfile
   output, messages and error beeps. For configuration, environment variables
   can be used:
                           Values
      Environment var.  Default  CID
      DOSBOX_INSTCID       0      1 (1 sets all other values)
      DOSBOX_INSTLOG       1      1
      DOSBOX_INSTMSG       1      0
      DOSBOX_INSTBEEP      0      0

   The default installation method is manually. Therefore both log file
   output and messages are activated. 'Messages' means that in case of an
   error, message boxes pop up that need interaction. For an automated (CID)
   installation, these messages are unwanted. To achieve that, set the
   environment variable

      DOSBOX_INSTCID=1

   __________________________________________________________________________
   Log files

   The log file is named dosbox_inst.log. It is usually written to the
   directory pointed to by the environment variable LOGFILES. Its value is
   usually:

      <boot_drive>\var\log

   If that directory doesn't exist, it is created in DOSBox\inst. If the
   DOSBox installation directory is not found, it is created in the path of
   the WarpIN archive.

   Three generations of LOG files are kept:

      dosbox_inst.log    (newest one)
      dosbox_inst_2.log
      dosbox_inst_3.log

   __________________________________________________________________________
   REXX version

   The installation was tested with Classic REXX. It may lead to
   unpredictable results when Object REXX is used.


_____________________________________________________________________________

   Basic configuration
_____________________________________________________________________________

   For configuration, the file 'dosbox.conf' in the directory of 'dosbox.exe'
   (dosbox directory) can be used. For OS/2, an English version is copied
   from the 'eng' subdirectory to the dosbox directory, but only, if it
   doesn't already exist.

   __________________________________________________________________________
   Language

   To activate one of the optionally installed .lng or .lang files, ensure
   that dosbox.conf contains the following entry:

      [dosbox]
      language=<language_filename>

   <language_filename> should be replaced by e.g. 'deu.lng'. This file should
   either be placed in the directory of 'dosbox.exe' or the 'language' value
   must also include the subpath or full path of that .lng file. This entry
   must match and the file must exist. Otherwise DOSBox creates a trap on its
   start.

   Alternatively, you can also use the 'dosbox.exe' parameters:

     -lang <language_filename>
     -conf <config_filename>

   __________________________________________________________________________
   Keyboard

   In the OS/2 version, the keyboard layout is not selected automatically.
   The 'auto' value for 'keyboardlayout', which is the default, doesn't seem
   to work:

      [dos]
      keyboardlayout=auto

   It can be changed by changing the 'keyboardlayout' value. E.g. for using
   German keyboard layout with the default codepage 858 (similar to 850, but
   contains the Euro sign), add this to 'dosbox.conf':

      [dos]
      keyboardlayout=gr

   Alternatively, it can be changed with the 'keyb' command:

      [autoexec]
      keyb gr

   Some usual keyboard layout values for existing translations:

      us       eng  English
      gr       deu  German
      fr       fra  French
      it       ita  Italian
      no       nor  Norwegian
      ru       rus  Russian
      cz       cze  Czech
      dk       dan  Danish
      es       esp  Spanish
      fi       fin  Finnish
      hu       hun  Hungarian
               kor  Korean (DBCS)
      nl       ned  Dutch
      pl       pol  Polish
      po       prt  Portuguese
      tr       tur  Turkish

   See the table in 'KEYB\layouts.txt', column 'File' for more keyboard
   layouts and section '8. Keyboard Layout' in 'README'.

   Also bundled is mKEYB, a replacement of KEYB, which has the keyboard
   tables compiled in. See the help file in 'mkeyb\README.TXT'.

   __________________________________________________________________________
   Configuration file with NLS comments

   A recent and complete config file with NLS comments can be created as a
   starting point:

      o  Add the language file and the keyboard layout values to
         'dosbox.conf', as described above.

      o  Start 'dosbox.exe' with an existing 'dosbox.conf'.

      o  From the host system, rename 'dosbox.conf' to 'dosbox.conf.bak'.

      o  Export the current configuration, together with NLS comments to the
         dosbox directory:

            config -wcp dosbox.conf

         This new file contains the values of the renamed file 'dosbox.conf'
         from the startup of DOSBox and NLS comments, if the 'language'
         value was configured before.

   You can also use one of the examples in the NLS subdirectories as
   template.

   __________________________________________________________________________
   Mount host directories as local drives

   For mounting host directories, use the mount command:

      [autoexec]
      mount <local_drive_letter> <host_dir>

   Example:

      mount D F:\Apps\DOSBox

   __________________________________________________________________________
   Further information

   See the detailed descriptions in 'README', sections '4. Internal Programs'
   and '3. Command Line Parameters'.

Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 01:47:12 am
It's likely the updated stdcpp6. Try updating again, yum update, and if that doesn't fix the issue, file an issue at Bitwises Github, probably under GCC.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 24, 2020, 02:46:34 am
Hi All

I had the following release of dosbox 0.74 installed which worked fine on ArcaOS5.0.4:-

    8-07-15  9:26p     3,188,956    342 a---  dosbox.exe

Just downloaded and installed DOSBOX0.74_30.03.19.EXE to update existing installation. Works fine - even after I manually deleted all the *.dll support files previous versions used.

Not sure what libs this build requires but libc, libgcc, libstdc++6 are current.
Dropping dosbox.exe onto PMdll suggests those are the only *nixy support files needed.


Regards

Pete
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 24, 2020, 03:54:17 am
Hi All

I may have found the dosbox problem...

After updating libstdc++ to 9.2.0-4 which dragged in gcc-stdc++-shared-library 4.4.6-15 (not previously installed) I now find dosbox does not work.

I tried to "Downgrade" libstdc++ to the previous installed version which worked, 4.4.6.17-1.oc00.
This fails with this ANPM "Download Failed" message displayed:-


   An error occurred when trying to download or install packages.

   djvulibre-3.5.27-3.oc00.i686 requires stdcpp6.dll


The above error not seen prior to installing libstdc++ to 9.2.0-4 and gcc-stdc++-shared-library 4.4.6-15 just a few minutes previously.

Do other users have the above suspect files installed?

It also looks like the above installation has resulted in libstdc++6 and libsupc++6 no longer being displayed as "Installed" by ANPM which shows them as "Available".

However, trying to Install either of those libraries or "Downgrade" them results in a message that the packages are already installed, nothing to do...

How do I resolve the following problems:-

1] "Downgrade" libstdc++ to 4.4.6.17-1.oc00?

2] (Re)Install libstdc++6 and libsupc++6


Regards

Pete




Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 04:05:02 am
You could try, on a command line
Code: [Select]
yum downgrade libstdc++
and keep adding other packages that yum complains about,
Code: [Select]
yum downgrade libstdc++ djvulibre
etc.
Really someone needs to open an issue and let the developers know about this problem and hopefully they can fix. Baring a fix, things will need recompiling
Title: Re: DOSBox Issue - STDCPP6?
Post by: Martin Iturbide on May 24, 2020, 04:28:32 am
Hi

From ANPM I get the following errors when trying to downgrade libstdc++.
Quote
splix-2.0.0-2.i686 requires stdcpp6.dll
qt5-designer-5.13.1-1.oc00.i686 requires stdcpp6.dll
brlaser-4.0.0-0.i686 requires stdcpp6.dll
qt5-qtbase-devel-5.13.1-1.oc00.i686 requires stdcpp6.dll

With "yum downgrade libstdc++" I get:

Quote
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.i686 0:9.2.0-2.oc00 will be a downgrade
--> Processing Dependency: libgcc = 9.2.0-2.oc00 for package: libstdc++-9.2.0-2.
oc00.i686
---> Package libstdc++.i686 0:9.2.0-4.oc00 will be erased
--> Finished Dependency Resolution
Error: Package: libstdc++-fwd-9.2.0-4.oc00.i686 (installed)
           Requires: libstdc++ = 9.2.0-4.oc00
           Removing: libstdc++-9.2.0-4.oc00.i686 (installed)
               libstdc++ = 9.2.0-4.oc00
           Downgraded By: libstdc++-9.2.0-2.oc00.i686 (netlabs-rel)
               libstdc++ = 9.2.0-2.oc00
           Available: libstdc++-4.4.6.17-1.oc00.i386 (netlabs-rel)
               libstdc++ = 4.4.6.17-1.oc00
Error: Package: libstdc++-9.2.0-2.oc00.i686 (netlabs-rel)
           Requires: libgcc = 9.2.0-2.oc00
           Installed: libgcc-9.2.0-4.oc00.i686 (installed)
               libgcc = 9.2.0-4.oc00
           Available: libgcc-9.2.0-2.oc00.i686 (netlabs-rel)
               libgcc = 9.2.0-2.oc00
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


It seems it will give me some trouble to downgrade.

I will try it just to test if DOSBox works again.

Regards
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 05:02:47 am
Here is a rebuilt dosbox.exe. Move all DLLs and dosbox.exe out of your dosbox install directory, I'd just create a bak directory or such and move them there, then unzip this one into your dosbox install directory and test. All I know is that it started up here.
Edit: this uses the latest DLLs from netlabs-rel including SDL.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 24, 2020, 06:00:53 am
Hi All

Both the problems are explained by use of yum on the command line:-

[J:\USR\BIN]yum install libstdc++6
Setting up Install Process
Package libstdc++6-4.9.2.1-3.oc00.i686 is obsoleted by libstdc++-9.2.0-4.oc00.i6
86 which is already installed
Nothing to do

The same message is displayed when trying to install libsupc++6.

Would have been helpful to see that message in ANPM...

Installed Daves dosbox-074.3 which works fine.

So, Thank you Dave for both the dosbox build and the suggestion of using yum directly.


Regards

Pete


Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 06:47:04 am
Update about my build, seems here it is using SDL12.DLL in @unixroot\usr\local\lib, not the RPM installed one. They both have the same name and presumably the same exports so should be interchangable, but who knows until tested.
This is just the latest tarball from sourceforge that I built as I couldn't find the source that Josh used. Luckily he/someone seems to have got the OS/2 patches committed upstream.
As for downgrading libstdc++, so much is going to depend on it as it is a basic system type library that downgrading isn't advised.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Sigurd Fastenrath on May 24, 2020, 08:07:42 am
Had the same issue, resolved it by only replacing the SDL.DLLs with those from Version

SDL-1215-20160303.zip

Have not seen any sideeffects on other appplications so far.

This is what popuplog looked like before:

05-24-2020  07:22:32  SYS2070  PID 0039  TID 0001  Slot 008f
C:\APPS\SYSTEM\DOSBOX\DOSBOX.EXE
DOSBOX->STDCPP6.__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE
127
------------------------------------------------------------

05-24-2020  07:22:39  SYS2070  PID 003a  TID 0001  Slot 008f
C:\APPS\SYSTEM\DOSBOX\DOSBOX.EXE
DOSBOX->STDCPP6.__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE
127
------------------------------------------------------------

05-24-2020  07:22:43  SYS2070  PID 003b  TID 0001  Slot 008f
C:\APPS\SYSTEM\DOSBOX\DOSBOX.EXE
DOSBOX->STDCPP6.__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE
127
------------------------------------------------------------

05-24-2020  07:24:02  SYS2070  PID 003c  TID 0001  Slot 008f
C:\APPS\SYSTEM\DOSBOX\DOSBOX.EXE
DOSBOX->STDCPP6.__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE
127
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 08:41:09 am
wchar() problem? Wonder if all translations will be handled? There's been quite a few wchar() fixes that come with GCC9.9.2. wchar = wide char = utf8 or utf16.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Sigurd Fastenrath on May 24, 2020, 09:00:25 am
 I have to correct myself: my problem was not having this sigserv message, it was that dosbox only starts once, if at all, but never for a second time. Most times (99%) the program window appeared with no message, only a black screen,  and freezed the system.

It is resolved with the sdl.dlls as I described. I was misleaded because I had this STDCPP6 message in popuplog, that was mentoined in this thread here as well. Anyway, sorry.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Martin Iturbide on May 24, 2020, 02:47:08 pm
Thanks Dave.

Your recompiled version save me a lot of trouble.

Regards
Title: Re: DOSBox Issue - STDCPP6?
Post by: David Graser on May 24, 2020, 04:21:31 pm
Thanks Dave.

Your recompiled version save me a lot of trouble.

Regards
Dave's version fixed the STDCPP6 problem for me.  I am using all the latest updates from Bitwise Works.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 06:49:23 pm
Does anyone use networking with DOSBox?
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 24, 2020, 08:30:07 pm
Hi Dave,

your build fixes the issue for me as well, great!

What still doesn't work, is dosbox_rec.exe, The "Recompiling" variant of dosbox.exe. I asked Jochen about the difference to the normal version, but can't remember/find his explanation.

BTW: I have a full-featured installer ready since last summer. I have to contact Jochen again.

To your question: No, I don't have tested DOSBox/2 over network. In fact, I don't use DOSBox/2 at all, just made the install scripts.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 24, 2020, 08:57:30 pm
... and the .wpi builds, installs and works well. I've just tested my newly-built dosbox074_2020-05-24.wpi. It installs also the .xqs file without modification of the creation script.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 24, 2020, 09:32:35 pm
About the "Recompiling"-Variants: I've found Jochen's answer. Roughly translated:

Jochen wrote: Recompiling is a kind of JIT. This option exists only for the x86 versions of DOSBox. Furthermore he wrote that he decided to create another .exe for that 16 years ago, but had also the idea how to add that feature to the configuration.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 24, 2020, 10:52:12 pm
Hi Andreas,
I just basically used the defaults for building, ran autogen.sh to create OS/2 configure, makefile-in's and such then
Code: [Select]
sh configure "LDFLAGS=-Zomf -Zmap -Zhigh-mem" LIBS=-lcx
Looking at the INSTALL file, I see these configure options,
Quote
--disable-dynamic-x86
        disables the dynamic x86 specific cpu core. Although it might be
        be a bit unstable, it can greatly improve the speed of dosbox on x86
        hosts.
        Please note that this option on x86 will result in a different
        dynamic/recompiling cpu core being compiled then the default.
        For more information see the option --disable-dynrec

--disable-dynrec
        disables the recompiling cpu core. Currently x86 and x86_64 only.
        You can activate this core on x86 by disabling the dynamic-x86 core.
So it seems the recompiling variant is the default. I could easily build another binary with these options if requested. I guess after 16 years the recompiling option is mature, or perhaps the INSTALL file is not clear.
Other possible options include compiling with the debugger enabled, introduces a ncurses dependency. Using SDL-NET for modem and IPX support, SDL-SOUND to support mp3/ogg audio tracks on some diskimages.
Don't know if Jochan is still active, if not I can build whatever if you want to package it.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 25, 2020, 08:06:19 am
Update about my build, seems here it is using SDL12.DLL in @unixroot\usr\local\lib, not the RPM installed one. They both have the same name and presumably the same exports so should be interchangable, but who knows until tested.
This is just the latest tarball from sourceforge that I built as I couldn't find the source that Josh used. Luckily he/someone seems to have got the OS/2 patches committed upstream.
As for downgrading libstdc++, so much is going to depend on it as it is a basic system type library that downgrading isn't advised.
Hi, I always use the DOSBOX official repo for new versions. When I had something to change, I sent a patch to the maintainers.
So, compiling the tarball / SVN version, is the correct thing to do.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 25, 2020, 08:16:07 am
Hi Andreas,
I just basically used the defaults for building, ran autogen.sh to create OS/2 configure, makefile-in's and such then
Code: [Select]
sh configure "LDFLAGS=-Zomf -Zmap -Zhigh-mem" LIBS=-lcx
Looking at the INSTALL file, I see these configure options,
Quote
--disable-dynamic-x86
        disables the dynamic x86 specific cpu core. Although it might be
        be a bit unstable, it can greatly improve the speed of dosbox on x86
        hosts.
        Please note that this option on x86 will result in a different
        dynamic/recompiling cpu core being compiled then the default.
        For more information see the option --disable-dynrec

--disable-dynrec
        disables the recompiling cpu core. Currently x86 and x86_64 only.
        You can activate this core on x86 by disabling the dynamic-x86 core.
So it seems the recompiling variant is the default. I could easily build another binary with these options if requested. I guess after 16 years the recompiling option is mature, or perhaps the INSTALL file is not clear.
Other possible options include compiling with the debugger enabled, introduces a ncurses dependency. Using SDL-NET for modem and IPX support, SDL-SOUND to support mp3/ogg audio tracks on some diskimages.
Don't know if Jochen is still active, if not I can build whatever if you want to package it.
I'm sort of. I got distracted by some other projects and life in general. I will try to build a new package with Andreas great package scripts in next few days.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 25, 2020, 01:16:52 pm
Does anyone of you have netlabs-exp activated. I can't upgrade to GCC 9, because a dependency is missing.

PS: Yes, I'll file a ticket, if I can't resolve this issue.
 
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dariusz Piatkowski on May 25, 2020, 02:48:38 pm
Hi Jochen,

Does anyone of you have netlabs-exp activated. I can't upgrade to GCC 9, because a dependency is missing...

Yes, what info are you looking for?

For the record, here is my netlabs-exp.repo content:

Code: [Select]
[G:\etc\yum\repos.d]type netlabs-exp.repo
[netlabs-exp]
name=Netlabs - Experimental Repo
baseurl=http://rpm.netlabs.org/experimental/$releasever/$basearch/
enabled=1

...everyone has access to this, right?
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 25, 2020, 03:46:59 pm
Hi Jochen

Presuming you are using ANPM - Arca Noae Package Manager from https://www.arcanoae.com/resources/downloadables/arca-noae-package-manager/ - you need to add the repo to the available repos list.

With ANPM running click Manage -> Repositories to open the Manage Respositories window.

Click Repository -> Add -> *YUM Repository and fill in the Add Repository form with these details:-

Name: Netlabs - Experimental Repo
Description: Netlabs experimental repository 00 - i386
URI: http://rpm.netlabs.org/experimental/$releasever/$basearch/

Then click Save.

You should then find netlabs-exp listed as Available, select and install.

Hopefully, if I have not forgotten a step, you should now have access to netabs-exp.


Regards

Pete



Title: Re: DOSBox Issue - STDCPP6?
Post by: Silvan Scherrer on May 25, 2020, 03:54:54 pm
Does anyone of you have netlabs-exp activated. I can't upgrade to GCC 9, because a dependency is missing.

PS: Yes, I'll file a ticket, if I can't resolve this issue.
There should not be anything missing. Please try again. Init still doesnt work with netlabs-rel post the output please.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 25, 2020, 04:27:42 pm
Hi Silvan, this is still broken. After a yum clean all,
Code: [Select]
--> Finished Dependency Resolution
Error: Package: mpc-devel-1.0.1-3.i686 (@netlabs-rel)
           Requires: libmpc3 = 1.0.1
           Removing: libmpc3-1.0.1-3.i686 (installed)
               libmpc3 = 1.0.1-3
           Obsoleted By: libmpc-1.1.0-1.oc00.i686 (netlabs-rel)
               libmpc3 = 1.1.0-1.oc00
           Available: libmpc3-1.0.1-1.i686 (netlabs-rel)
               libmpc3 = 1.0.1-1
           Available: libmpc3-1.0.1-2.i686 (netlabs-rel)
               libmpc3 = 1.0.1-2
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 25, 2020, 05:08:32 pm
Update about my build, seems here it is using SDL12.DLL in @unixroot\usr\local\lib, not the RPM installed one. They both have the same name and presumably the same exports so should be interchangable, but who knows until tested.
This is just the latest tarball from sourceforge that I built as I couldn't find the source that Josh used. Luckily he/someone seems to have got the OS/2 patches committed upstream.
As for downgrading libstdc++, so much is going to depend on it as it is a basic system type library that downgrading isn't advised.
Hi, I always use the DOSBOX official repo for new versions. When I had something to change, I sent a patch to the maintainers.
So, compiling the tarball / SVN version, is the correct thing to do.

Good to send your patches upstream but you need a link on your page pointing to sourceforge as it took me a while to figure out.
Thanks for maintaining.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 26, 2020, 08:50:09 am
Good to send your patches upstream but you need a link on your page pointing to sourceforge as it took me a while to figure out.
Thanks for maintaining.
Correct. I didn't think that someone would want to compile it herself.
I will put a link on my page.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Silvan Scherrer on May 26, 2020, 09:00:26 am
Hi Silvan, this is still broken. After a yum clean all,
Code: [Select]
--> Finished Dependency Resolution
Error: Package: mpc-devel-1.0.1-3.i686 (@netlabs-rel)
           Requires: libmpc3 = 1.0.1
           Removing: libmpc3-1.0.1-3.i686 (installed)
               libmpc3 = 1.0.1-3
           Obsoleted By: libmpc-1.1.0-1.oc00.i686 (netlabs-rel)
               libmpc3 = 1.1.0-1.oc00
           Available: libmpc3-1.0.1-1.i686 (netlabs-rel)
               libmpc3 = 1.0.1-1
           Available: libmpc3-1.0.1-2.i686 (netlabs-rel)
               libmpc3 = 1.0.1-2
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
On my system, YUM can't find mpfr6.dll.
to see whats wrong we need the yum log. everything else tells not really much. As Dave's issue was different and a one time issue. If you face the mpc-devel issue you have to uninstall mpc-devel. and then it should run.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 26, 2020, 09:09:39 am
A reboot later, I was able to update everything.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 26, 2020, 04:22:10 pm
Hi Dave

I think I have found a minor problem with your DOSBox build or the support files used.

AS i do not have DOS/Win16 support installed I have been using DOSBox to provide DOS window/fullscreen ~Command Prompts for very occasional use.

This worked fine until DOSBox and libstdc++ (9.2.0-4) updates.

Now DOSBox fullscreen works OK but something is adding to the dosbox,conf when using DOSBox window.

This is the end of my dosbox.conf file:-

[autoexec]
# Lines in this section will be run at startup.
mount e e:
e:


Works fine for -fullscreen, used to work fine for window as well.

When I start a DOSBox window the above mount lines happen then some more commands appear from somewhere and this happens:-

E:\>MOUNT C "H:\DESKTOP"
Drive C is mounted as local directory "H:\Desktop\"

E:\>C:

C:\>


Using -conf to point to my dosbox.conf (which should be the default to use anyway) gives the same result.

As the above MOUNT C is not part of my dosbox.conf and only happens in window mode, not -when using -fullscreen, Is it a DOSBox problem?


Just to confuse the issue: If I start a DOSBox window from the XWorkplace Configuration Folder -> ~Command Prompts -> ~DOS Window all works as it should.

The problem with the unknown lines above only occurs when I Right Mouse Button click and select Command prompts -> DOS Window in which case wherever I have selected to open a DOS Window becomes the mount directory eg RMB on folder K:\Programs and open a DOS Window results in "K:\Programs" as the directory mounted as C:\> .

Having typed the above I am now wondering if it could be XWorkplace related...

Any Ideas?


Regards

Pete
Title: Re: DOSBox Issue - STDCPP6?
Post by: Dave Yeo on May 26, 2020, 04:58:40 pm
Sounds to me that the system is somehow passing a cmd line parameter to DOSBox. You could try running dosbox.exe --help or dosbox.exe --help | less to look at possibilities.
Right now I'm booted to a new beta install of AOS and testing the default install and my DOSBox build is crashing with
Code: [Select]
05-26-2020  07:45:34  SYS2070  PID 00dd  TID 0001  Slot 00e5
K:\USR\LOCAL\SRC\DOSBOX-0.74-3\SRC\DOSBOX.EXE
DOSBOX->STDCPP6.__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE
127
So it needs the newer stdcpp6. I'll do a yum update later and retest.
BTW, I filed an issue with Bitwise, their response that this is only the second program to have an issue and since it can be rebuilt and they don't have the resources to debug, won't fix.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Sandra Asja Eickel on May 26, 2020, 07:12:20 pm
Presuming you are using ANPM [...] you need to add the repo to the available repos list.

With ANPM running click Manage -> Repositories to open the Manage Respositories window.
Click Repository -> Add -> *YUM Repository and fill in the Add Repository form with these details:
[...]
Hopefully, if I have not forgotten a step, you should now have access to netabs-exp.

That's the old and hard way.

As long as you have netlabs-rel as repo, installing the package netlabs-exp is all you need to do.

Greetings,
Sandra-Asja
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 26, 2020, 07:37:32 pm
Hi Sandra-Asja

Thanks for the update - I obviously have not had to perform this action since the "old and hard way" was the only way  :-)


Regards

Pete
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 26, 2020, 08:45:45 pm
[autoexec]
mount e e:
e:
That works for me both in full screen and in window mode. In your example it's strange that it uses C: instead of the specified E drive letter. Z: is the system drive.

I'm using Dave's build he has posted here (https://www.os2world.com/forum/index.php?action=dlattach;topic=2455.0;attach=6333).
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 26, 2020, 08:46:55 pm
Hi Dave

I think I have found a minor problem with your DOSBox build or the support files used.

AS i do not have DOS/Win16 support installed I have been using DOSBox to provide DOS window/fullscreen ~Command Prompts for very occasional use.

This worked fine until DOSBox and libstdc++ (9.2.0-4) updates.

Now DOSBox fullscreen works OK but something is adding to the dosbox,conf when using DOSBox window.

This is the end of my dosbox.conf file:-

[autoexec]
# Lines in this section will be run at startup.
mount e e:
e:


Works fine for -fullscreen, used to work fine for window as well.

When I start a DOSBox window the above mount lines happen then some more commands appear from somewhere and this happens:-

E:\>MOUNT C "H:\DESKTOP"
Drive C is mounted as local directory "H:\Desktop\"

E:\>C:

C:\>


Using -conf to point to my dosbox.conf (which should be the default to use anyway) gives the same result.

As the above MOUNT C is not part of my dosbox.conf and only happens in window mode, not -when using -fullscreen, Is it a DOSBox problem?


Just to confuse the issue: If I start a DOSBox window from the XWorkplace Configuration Folder -> ~Command Prompts -> ~DOS Window all works as it should.

The problem with the unknown lines above only occurs when I Right Mouse Button click and select Command prompts -> DOS Window in which case wherever I have selected to open a DOS Window becomes the mount directory eg RMB on folder K:\Programs and open a DOS Window results in "K:\Programs" as the directory mounted as C:\> .

Having typed the above I am now wondering if it could be XWorkplace related...

Any Ideas?


Regards

Pete
I can't reproduce this problem with my new build. In window mode every command in [autoexec] is executed. Did you try to execute Dosbox from the shell without parameters?

Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 26, 2020, 08:48:03 pm
To avoid confusion: netlabs-exp is not required to run that build. According to Silvan and Jochen, it even builds without it.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 26, 2020, 09:31:02 pm
Here you go. I built a recent package. Only difference to upstream is some code that prevents a crash from a CTRL+F9 exit.
Can somebody please test the WPI package?
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 26, 2020, 10:14:21 pm
I have two problems:

1) All four program objects close just after start. I see a window flashing. That did't happen with Dave's build. (ANPM showed a few days ago that every .rpm is recent.)

2) The WarpIN installation complains that the file README.OS2 already exists with a newer date. On scanning the archive, I find it only in package 1. I can't explain that, esp. because on the second try, I have wiped the destination dir before. (But the installation marks all existing files with an EA, so that no old files should exist after installation.)
That requires user input. It doesn't matter which option is selected.

Question: Don't you want to activate the touch option?

Here's the command line output from the failed start:
Code: [Select]
epm: C:\Programs\DOSBox > dosbox.exe
DOSBox version SVN
Copyright 2002-2020 DOSBox Team, published under GNU GPL.
---
CONFIG: Loading primary settings from config file dosbox.conf
Your fullscreen resolution can NOT be determined, it's assumed to be 1024x768.
Please edit the configuration file if this value is wrong.
terminate called after throwing an instance of 'char*'

Killed by SIGABRT
pid=0x065d ppid=0x065b tid=0x0001 slot=0x00a8 pri=0x0214 mc=0x0001 ps=0x0010
C:\PROGRAMS\DOSBOX\DOSBOX.EXE
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

epm: C:\Programs\DOSBox >

And here's the output from popuplog.os2:

Code: [Select]
------------------------------------------------------------

05-26-2020  21:53:29  SYS2070  PID 05da  TID 0001  Slot 009f
F:\APPS\DOSBOX\DOSBOX.EXE
DOSBOX->LIBCN0.1988
182

Interesting, libcn0.dll.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 26, 2020, 10:59:04 pm
It works now!

I had to update the .rpm packages again. libc was available in a newer version. (I guess that one contains libcn0.dll, but I wonder why they're not compatible.) I have installed that with ANPM. Due to its package priority list, libc installation forces a reboot.

After that, The next package shows endless repeating that it downloads gmp.

I killed anpm.exe and python.exe and then executed in a command line:

Code: [Select]
yum update
That works. It installs all the remaining 11 packages, including gmp. After that, I started ANPM again and it shows that all packages are recent.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 27, 2020, 12:33:00 am
Hi Jochen

Yes the [autoexec] statements work fine.

The problem is the extra commands not in dosbox.conf that then happen ie mounting the selected drive or folder as C:\>


Regards

Pete
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 27, 2020, 07:04:05 am
Hi Jochen

Yes the [autoexec] statements work fine.

The problem is the extra commands not in dosbox.conf that then happen ie mounting the selected drive or folder as C:\>


Regards

Pete
Oh ok. I misuderstood. Do you have a example how the commands are called?
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on May 27, 2020, 07:06:49 am
Question: Don't you want to activate the touch option?
Is this an option in your installer package?
Title: Re: DOSBox Issue - STDCPP6?
Post by: Rich Walsh on May 27, 2020, 07:46:31 am
The problem is the extra commands not in dosbox.conf that then happen ie mounting the selected drive or folder as C:\>

If you don't want the WPS to pass the name of the directory whose menu you used, put a percent sign (%) in the 'Parameters' field of the relevant program object.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Pete on May 27, 2020, 01:53:06 pm
Hi Rich

Thank You, that is what I had forgotten about setting up a DOSBox Command Prompt window.


Regards

Pete

Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on May 28, 2020, 01:04:47 am
Question: Don't you want to activate the touch option?
Is this an option in your installer package?
Yes, dosbox-createwpi.cmd, line 211.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Martin Iturbide on June 02, 2020, 04:26:46 pm
Hi Jochen

Do you think it will be ok to update update your page with this new update?
https://www.joschs-robotics.de/dosbox/dosbox.html

It works for me, but I don't know if there are more comments.

Regards
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on June 02, 2020, 04:31:36 pm
Do you think it will be ok to update update your page with this new update?
https://www.joschs-robotics.de/dosbox/dosbox.html
Just wait a bit. Jochen will probbaly upload an official version to Hobbes.

(@Jochen: Use passive FTP.)
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on June 02, 2020, 04:33:42 pm
Do you think it will be ok to update update your page with this new update?
https://www.joschs-robotics.de/dosbox/dosbox.html
Just wait a bit. Jochen plans to upload a new version to his site.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on June 04, 2020, 01:05:01 pm
Hi.

I will upload the new package to my site and possibly to Hobbes, but first I have to figure some packaging problem out.


Bye Jochen
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on June 06, 2020, 08:51:36 pm
I just uploaded the newest package of DOSBOX/2 to my website. As usual, you find it here: https://www.joschs-robotics.de/dosbox/dosbox.html (https://www.joschs-robotics.de/dosbox/dosbox.html).
Title: Re: DOSBox Issue - STDCPP6?
Post by: Andreas Schnellbacher on June 07, 2020, 01:38:47 am
Thanks for this. It behaves for me the same as the previously installed package, except that the files show now the same date. An exception is dosbox.conf, which is correctly edited by the installation. I've tested eng and deu languages. Both work, including their installations.

I see that you've removed eng\COPYING.LIB and eng\INSTALL. Both were present before, but not marked with the obsolete EA nor removed. Strange, but minor and not worse to change anything.
Title: Re: DOSBox Issue - STDCPP6?
Post by: Jochen Schäfer on June 08, 2020, 10:54:54 am
I don't know, that I actively removed them. I just activated automatic download for the language and keyboard files.