I am having troubles compiling this ebuild. Have upgraded yesterday to GCC 4.1.1 and the new glibc, followed the upgrade guide. Maybe GCC 4.1.1 related?
Created attachment 95630 [details] The console output of the emerge
Created attachment 95631 [details] emerge --info
Try with 1.3.2, please.
Okay that worked. (altough ~x86) Thanks.
Good, thanks. ;)
dosemu-1.3.2 is broken with autoconf-2.60 (bug #138327). should that block this?
*** Bug 146104 has been marked as a duplicate of this bug. ***
I have recently moved from gcc-3.4.6-r1 to gcc 4.1.1 (and even today to gcc-4.1.1-r1), and dosemu-1.3.2 does not compile with the flags I'm usually using. They are: CFLAGS="-O2 -march=pentium-m -fomit-frame-pointer -fforce-addr -fprefetch-loop-arrays -falign-functions=64 -finline-functions -fweb -pipe" I was playing with them, guessing which was the buggy one, and I found that '-finline-functions' was guilty. dosemu did compile with gcc-3.4.6-r1 and these flags, so I think there is a bug related to this flag.
I've now added 1.3.3, please don't mark 1.3.2 stable, it's broken as hell. Wait some time till we've sorted out all maybe upcoming issues on 1.3.3 and mark that stable then. About the -finline: Can you try 1.3.3?
dosemu-1.3.3 USE="X gpm -debug -svga" seems to be ok at a first glance for me on x86, apart from: QA Notice: the following files contain executable stacks Files with executable stacks will not work properly (or at all!) on some architectures/operating systems. A bug should be filed at http://bugs.gentoo.org/ to make sure the file is fixed. For more information, see http://hardened.gentoo.org/gnu-stack.xml Please include this file in your report: /var/tmp/portage/dosemu-1.3.3/temp/scanelf-execstack.log "RWX --- --- usr/bin/dosemu.bin" Just because there is an ongoing discussion about CFLAGs: CFLAGS="-march=athlon-xp -O2 -pipe" Please note, that i have not yet tried to run some external dos software ...; i'll look after this in the next few days.
btw.: if i should attach var/tmp/portage/dosemu-1.3.3/temp/scanelf-execstack.log, let me know ...
i've now tested dosemu-1.3.3 USE="X gpm -debug -svga" with two old dos-games. seems to work so far ...
however, maybe it is of intererst, that i get the following message when i start dosemu: You do not have the DOSEMU vga font installed and are running remote X. You need to install the vga font on your _local_ Xserver. Look at the readme for details. For now we start with an fixed font, which does not display all national characters correctly. ... be warned
Note that the same compilation error occurs with 1.2.2-r1, which is the last stable, so that should be fixed too unless 1.3.3 is gonna get declared as stable real soon.
Just to confirm that 1.3.3 compiles on my stable system with the current stable gcc-4.1: Using built-in specs. Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.1.1 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libmudflap --disable-libssp --enable-java-awt=gtk --enable-languages=c,c++,java --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 4.1.1 (Gentoo 4.1.1) The emulator seems to work (I only tested it briefly), but it produces the same warning about fonts that comment #13 has mentioned.
1.3.3 gives me this error when executing (as normal user or root) ERROR: MAPPING: cannot map temp file pool, Operation not permitted I am getting the same font messages described previously.
Created attachment 96893 [details] emerge --info collision after 2nd emerge of app-emulation/dosemu-1.3.3 (First one succeeded with FEATURES including collision-protect.) existing file /usr/share/dosemu/commands/fossil.com is not owned by this package existing file /usr/share/dosemu/commands/emufs.sys is not owned by this package existing file /usr/share/dosemu/commands/ems.sys is not owned by this package existing file /usr/share/dosemu/commands/mgarrot.com is not owned by this package existing file /usr/share/dosemu/commands/cdrom.sys is not owned by this package existing file /usr/share/dosemu/commands/dumpconf.sys is not owned by this package existing file /usr/share/dosemu/commands/generic.com is not owned by this package existing file /usr/share/dosemu/commands/aspi.sys is not owned by this package existing file /usr/share/dosemu/commands/isemu.com is not owned by this package existing file /usr/share/dosemu/commands/eject.com is not owned by this package existing file /usr/share/dosemu/commands/unix.com is not owned by this package existing file /usr/share/dosemu/commands/cmdline.com is not owned by this package existing file /usr/share/dosemu/commands/xmode.com is not owned by this package existing file /usr/share/dosemu/commands/vgaoff.com is not owned by this package existing file /usr/share/dosemu/commands/blaster.com is not owned by this package existing file /usr/share/dosemu/commands/ecpuoff.com is not owned by this package existing file /usr/share/dosemu/commands/uchdir.com is not owned by this package existing file /usr/share/dosemu/commands/system.com is not owned by this package existing file /usr/share/dosemu/commands/dosdbg.com is not owned by this package existing file /usr/share/dosemu/commands/emumouse.com is not owned by this package existing file /usr/share/dosemu/commands/ugetcwd.com is not owned by this package existing file /usr/share/dosemu/commands/vgaon.com is not owned by this package existing file /usr/share/dosemu/commands/exitemu.com is not owned by this package existing file /usr/share/dosemu/commands/ecpuon.com is not owned by this package existing file /usr/share/dosemu/commands/speed.com is not owned by this package existing file /usr/share/dosemu/commands/bootoff.com is not owned by this package existing file /usr/share/dosemu/commands/lredir.com is not owned by this package existing file /usr/share/dosemu/commands/booton.com is not owned by this package
(In reply to comment #17) > collision after 2nd emerge of app-emulation/dosemu-1.3.3 > (First one succeeded with FEATURES including collision-protect.) > > existing file /usr/share/dosemu/commands/fossil.com is not owned by this > package hmm, i cannot reproduce this (just remerged dosemu-1.3.3 with collision-protect without any issues) ...
(In reply to comment #16) > 1.3.3 gives me this error when executing (as normal user or root) > > ERROR: MAPPING: cannot map temp file pool, Operation not permitted I had the same problem, but I fixed it with a configuration change. In /etc/dosemu/dosemu.conf I have modified $_mapping from "auto" to "mapashm". Try...
> I had the same problem, but I fixed it with a configuration change. In > /etc/dosemu/dosemu.conf I have modified $_mapping from "auto" to "mapashm". > Try... > Yes, it solved the problem. So, 1.3.3 is working fine for me. ------------ Portage 2.1.1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.17-gentoo-r8 i686) ================================================================= System uname: 2.6.17-gentoo-r8 i686 Intel(R) Celeron(R) CPU 2.40GHz Gentoo Base System version 1.12.5 Last Sync: Tue, 19 Sep 2006 00:50:01 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.3.5-r2, 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -pipe -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/NX/etc /usr/NX/home /usr/share/X11/xkb /usr/share/logwatch /var/www/localhost/htdocs/cacti/include" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O3 -pipe -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig collision-protect distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://linuv.uv.es/mirror/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" LINGUAS="" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apache2 berkdb bitmap-fonts bzip2 cli crypt dlloader dri eds elibc_glibc emboss encode fam foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 imlib input_devices_keyboard input_devices_mouse isdnlog jpeg kernel_linux libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls nptl nptlonly ogg pam pcre perl png pppd python qt3 qt4 quicktime readline reflection samba sdl session snmp spl sse sse2 ssl svg tiff truetype truetype-fonts type1-fonts udev usb userland_GNU video_cards_fglrx vorbis xml xmms xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
x86 is stable as the problem isn't a problem now apparently....
(In reply to comment #21) > x86 is stable as the problem isn't a problem now apparently.... I think the default config file should have been modified as explained in comment #19. (and put a link to this bug at that config file) I've just emerged dosemu-1.3.3 on a recently-updated-to-gcc-4.1 system, and I got the problem that can be solved as in comment #19.
