Wine is not the only thing that is having problems adapting to 64-bits.

[ericmatteson...@hotmail.com]

Written by Eric Matteson
Report on 64-bit Linux 12/19/2009
Wine is not the only thing that is having severe problems
with 64 bits.
Attempting to compile source tarballs for libgdiplus that is a
dependency
for both Linux mono for graphics programs and a wine that will run
Dot.NET
creates pointer related warnings (integers are too short to store 64-
bit
absolute memory addresses)
amd then mono for Linux is unable to display graphics in 64-bit Linux
as a result.
----------------------
In the much simpler c programming arena
the old Windows c programs edelev17.c text editor and dfrview2.c
picture viewer programs used to test the Star Wars Header file
bam10004.h that helps compile Windows c
programs onto Linux XWindows are disaster areas.
edelev17.c like most edelevxx text editors had code that
shared characters and pointers in the same implied common block
in memory.
Another large disaster was dfrview2.c which included
subroutines that called subroutines that called subroutines
that had an integer argument that passed a handle or pointer that
had to be lengthened to long in several places to pass the new
64-bit parameter that used to be 32-bit.
After a lot of fixing the new edeleb17.c text editor
and the new dfrview4.c *.bmp picture viewer program
( That are almost for WINDOWS ) can be compiled onto Linux
XWindows with the new bam10006.h header file.
In 32-bit Linux you can replace the
#include "bam10006.h"
line in edeleb17.c and dfrview4.c and compile them as
32-bit Windows programs using
winegcc -mwindows -o dfrview4.out dfrview4.c
if you built wine from a source tar.bz2 and
are on 32-bit Linux.
The reason that bam10006.h is needed is that wine is unlikely
to be installed sucessfully on 64-bit Linux anytime soon.
Some scripts on the Internet imply that 500 rpms have to be
installed in the correct order to build 32-bit XWindows
dependency libraries for wine.
There is no easy way to put wine on 64-bit Linux and the
hard way does not necessarrily work.
The reality is that bam10006.h IS COMPETING WITH WINE
for compiling Windows c programs on Linux. Both dfrview4.c
and edeleb17.c use
#include "bam10006.h"
instead of
#include <windows.h>
so they can be compiled directly onto Linux XWindows in
64-bit Linux in addition to traditional 32-bit Linux.
The fact that bam10006.h is one-bit-per-pixel is
NOT A PROBLEM because wine probably will NOT RUN AT ALL
on 64-bit Linux unless this very unfair COMPETITION
from bam10006.h pressures winemakers into adding a tarball
that can be compiled from source that will in a SINGLE TARBALL
compile the 32-bit dependency libraries for wine for
64-bit Linux in a SINGLE MAKE.
---------------------------------

[Link to edeleb17.c text editor program]
http://groups.google.com/group/comp.emulators.ms-windows.wine/msg/4bd0d55cc7c41825?dmode=source

[link to bam10006.h header to compile monochrome Windows programs
on Linux gcc ]
http://groups.google.com/group/comp.emulators.ms-windows.wine/msg/20a77f9271c981fc?dmode=source

[link to dfrview4.c *.bmp picture viewer program]
http://groups.google.com/group/comp.emulators.ms-windows.wine/msg/2fd6c288a99d0bc8?dmode=source

[link to (Everybody Hates Chris) episode complaining about problems
with 64-bit Linux]
http://groups.google.com/group/alt.tv/msg/5af980f924dd620f

[article about fixing broken linux (both 32 and 64-bits) that is not
linkable will be repeated next]
Pretend that you are enrolled in CS939 c++ programming course and you
have just found out that
Microsoft has discontinued Visual c++ 6.0 for Windows.
Chris on the Internet has stated that Linux can compile and run c++
programs
IF LINUX IS CORRECTLY AND COMPLETELY INSTALLED!!!!
First, you need to CHECK YOUR LINUX INSTALLATION
$ whereis c++
c++: /usr/bin/c++ /usr/include/c++
will list if Linux is correctly installed.
If you get just
c++:
then Linux is not installed correctly.
Reinstall Linux from the DVD or CDs with customize now
then in catagory
DEVELOPMENT
choose development tools and development libraries and
X software development
at beginning of Linux reinstall.
If you want to fix it without reinstalling and have high speed
Internet connected and IP address and DNS configured then login as
root user or use su
$ su
password:
# yum grouplist
to check the spelling of names of groups and then
# yum groupinstall "Development Tools"
# yum groupinstall "Development Libraries"
# yum groupinstall "X Software Development"
Answer y to all questions in the three yums.
# exit
then VERIFY your fixing with
$ whereis c++
$ whereis gcc
$ whereis stdio.h
All three should return non-null directories if Linux is
sucessfully FIXED.
For cs939 c++ class use
$ c++ progname.cpp -o progname.out
$ ./progname.out
to compile and run a CS939 c++ program.
Eric Matteson CS967