[SATLUG] run old software on new os

[Borries Demeler]

> 
> Yes, I found string.h in /usr/include and I included
> the kernel source at install.  I also decided to try
> the mandrake rpm, just for grins, and libasound.so.0
> and libvorbisfile.so.1 were missing dependencies.  I
> reinstalled mandrake 8.2 in some free space and then
> copied those files into /usr/lib.  Naturally, that

You aren't very clear about what exactly you copied.
Also, mixing rpms from Mandrake and Suse is not necessarily
a good idea. Did you just copy the library file or other
stuff as well?

After installing a new library, you need to run ldconfig
on your system to update the contents of the dynamic 
library search path. For that matter, if you don't like
to mix and match different distros and versions, you can
install the libs in a separate directory and simply add
this directory to /etc/ld.so.conf and then run ldconfig
again. It kinda helps to keep things separate that really
shouldn't be mixed.

> didn't work.  I didn't mention, I forced the install
> of the mandrake rpm and ldd  /usr/games/tuxpuck also
> indicated those two files missing.  Oh well, again, it
> certainly isn't critical, but I'm not ready to give
> up.  I guess I will try to learn more about the chroot
> approach.  One more thought, what about user mode

Yup, that would be my big suggestion. 

> linux.  Is it possible to install mandrake or the game
> in that way?  Thanks.


Here is what you do:

Set up a partition for your mandrake install on the same 
computer. Install it into the empty partition. Now you
have two choices:
1. make the partition bootable and add it to lilo so you
can boot into it. Compile your game on the original platform
and get it to work there.
2. boot into Suse and mount the partition under /mnt/mandrake
for example. Then issue the command: "chroot /mnt/mandrake"
and the system will run the mandrake distro files as you are 
booted into Suse. Use that environment to compile your program
under Suse. 

Once you got it running OK under either approach you can 
either reboot into Suse or exit the chroot environment and
copy the game to /usr/local/bin. When you run ldd it should
tell you whatelse you need to copy from the mandrake directory
to the /usr/local/lib directory (dont forget to run ldconfig!).

That should do the trick.

-Borries
> --- Borries Demeler <demeler at biochem.uthscsa.edu>
> wrote:
> 
> > > 
> > > Borries, I appreciate your thoughts.  Yeah, I
> > thought
> > > about the emulator approach, but don't have a
> > recent
> > > version of vmware.  Chroot is over my head, but I
> > do
> > > need to gain some comprehension of what can be
> > > accomplished using it.  I did eliminate virually
> > all
> > > errors by adding all available sdl, png, and jpg
> > > related files, programs I could find.  I still get
> > > "intro.c:92: warning: implicit declaration of
> > function
> > > `memset'
> > > make: *** [intro.o] Error 1".  I don't know if
> > that
> > > means anything to you.  Again thanks for your
> > help,
> > > I'm going to keep trying, mostly because I think
> > if I
> > > ever get this to work I will have learned
> > something. 
> > > Just imagine that!  Thanks.
> > 
> > memset is defined in string.h. make sure you have
> > string.h in your
> > include path. It should be part of the compiler but
> > also may be in the
> > kernel source, so make sure the kernel source is
> > installed.
> > 
> > Check to make sure you have it in /usr/include,
> > that's the standard
> > place for it.
> > 
> > -borries
> > 
> > 
> > >  
> > > --- Borries Demeler <demeler at biochem.uthscsa.edu>
> > > wrote:
> > > 
> > > > Hi Tim,
> > > > 
> > > > while not familiar with this particular
> > application
> > > > the problem you are
> > > > most likely running into are that the correct
> > > > versions of the includes
> > > > and libraries your application links against are
> > not
> > > > available. The
> > > > "substatial list of errors" is really your
> > friend
> > > > here, because it tells
> > > > you what is wrong. There are a number of ways to
> > go
> > > > around this. First,
> > > > see if the libraries and include files are
> > simply
> > > > missing or in locations
> > > > that are not in your search path. here the
> > solution
> > > > would be to simply
> > > > download them and add them to the search path.
> > the
> > > > compiler string may
> > > > need another line like this:
> > > > 
> > > > -I/usr/local/src/myoldincludes
> > > > -L/usr/local/src/myoldlibs
> > > > 
> > > > you want to make sure that don't overwrite newer
> > > > versions of the same
> > > > include files with older versions, so putting
> > them
> > > > in separate directories
> > > > is a *good idea*.
> > > > 
> > > > Libraries are generally versioned so you can put
> > in
> > > > an older version
> > > > without overwriting the newer one. But it may
> > still
> > > > be a good idea to
> > > > keep them in a separate directory because of the
> > > > symlink issue
> > > > 
> > > > Without seeing the "substantial list of errors"
> > I
> > > > can't really give you
> > > > any specific advice on how to solve this.
> > > > 
> > > > Another option is to install an older version of
> > > > Linux on a different
> > > > partition where the compilation environment is
> > > > compatible, compile
> > > > the application and then copy it and all the
> > > > necessary libs into the
> > > > newer version.
> > > > 
> > > > Another option would be to use VMWare to install
> > the
> > > > old version of
> > > > Mandrake on your current system and simply
> > compile
> > > > it there and then
> > > > copy stuff across to the new system.
> > > > 
> > > > Finally, you could simulate the same thing by
> > > > copying the entire old
> > > > Mandrake install into a subdirectory on your
> > Suse
> > > > install and then issue
> > > > the "chroot /tmp/mymandrakeinstall" command to
> > > > change the root to that
> > > > directory and then pretend you are running a
> > > > mandrake version. Then
> > > > Linux will just look in the standard places for
> > > > includes, compiler,
> > > > libs etc. The standard places will all be
> > relative
> > > > to the mandrake
> > > > install root, so it will use the older versions
> > > > instead of what's in
> > > > the regular places.
> > > > 
> > > > Personally, I prefer the latter option,
> > especially
> > > > since diskspace it
> > > > cheap and it is readily available for the next
> > time
> > > > you come across this
> > > > problem.
> > > > 
> > > > Hope that helps, -Borries
> > > > 
> > > > > 
> > > > > Hi, everyone.  I just recently subscribed to
> > your
> > > > list
> > > > > and am happy to see a lot of activity.  I
> > > > currently
> > > > > live in Corpus, and while the local group is
> > OK,
> > > > there
> > > > > just isn't much going on other than updating
> > > > machines.
> > > > >  I have a question that I feel should have an
> > easy
> > > > > answer, but I have been unable to find that
> > > > answer.  I
> > > > > am currently using SUSE 9.2 pro.  A game that
> > I
> > > > > discovered while using Mandrake 8.2 Tuxpuck,
> > > > doesn't
> > > > > compile on my new SUSE, or for that matter,
> > > > anything
> > > > > else I've tried.  That includes 
> > > > > a Red Hat, Fedora, SuSE 9.0, and Mandrake 10. 
> > The
> > > > > games version is tuxpuck-0.7.91.  The list of
> > > > errors
> > > > > is substantial.  I'm guessing what is going on
> > is
> > > > the
> > > > > sdl installed is newer and not compatible with
> > the
> > > > > required version.  This isn't terribly
> > important,
> > > > > obviously, but I read an interview with Linus
> > > > > recently, and he mentioned that software from
> > the
> > > > 90's
> > > > > will still work with modern Linux's.  More
> > recent
> > > > > version of Tuxpuck have installed OK, but it
> > is
> > > > the
> > > > > old version I enjoy.  Please excuse my
> > inability
> > > > to be
> > > > > concise and perhaps precise!  I'm a
> > construction
> > > > > worker! Ha!  Anyway, if anyone can point me in
> > the
> > > > > right direction I would appreciate it.  I do
> > my
> > > > own
> > > > > computers, and usually solve my own problems,
> > but
> > > > this
> > > > > one has me stumped.  Thanks.
> > > > > 
> > > > > 
> > > > > 		
> > > > > __________________________________ 
> > > > > Do you Yahoo!? 
> > > > > Meet the all-new My Yahoo! - Try it today! 
> > > > > http://my.yahoo.com 
> > 
> === message truncated ===
> 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Meet the all-new My Yahoo! - Try it today! 
> http://my.yahoo.com 
>  
> 
> _______________________________________________
> Satlug mailing list
> Satlug at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug
>