| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Maximus for Mandrake Linux |
DN> I downloaded the Unix version of Maximus 3.03b from the
DN> SourceForge website. Unfortunately it didn't compile and it
DN> produced quite a few error messages. I didn't capture the
DN> error messages as they went so quickly. I followed the
DN> instructions outlined in the readme file.
DN> I am trying to compile Maximus for Mandrake Linux 9.0. The
DN> last updated Maximus .gz file was back in June of 2003. Is
DN> that the latest version?
if you mean the max-3.03-etc.tar.gz file, yes... there is no other file
that i'm aware of... everything else has to come out of the cvs...
DN> I remember reading a couple weeks
DN> ago that someone found a way to strip the windows carriage
DN> returns out of the source code files. Thusly it would allow
DN> the compiler to properly compile the code?
that has been done and those files commited to the cvs... they were only
related to the sqafix code...
FWIW: here's my update script that i use to start clean and fresh, get the
cvs stuff, configure and compile...
===== start =====
cd /opt
rm -rf maximus
tar zxf max-3.03-etc.tar.gz
rm maxbuild?.log
rm maxbuild?.err
echo updating maximus from the cvs repository...
cvs -z3 -d :pserver:anonymous{at}cvs.sourceforge.net:/cvsroot/maximus co
maximus 1>opt/maxbuild1.log 2>/opt/maxbuild1.err
echo configuring... hit enter... possibly twice...
cd /opt/maximus
./configure --prefix=/opt/max 1>opt/maxbuild2.log 2>/opt/maxbuild2.err
echo running make build...
make build 1>/opt/maxbuild3.log 2>/opt/maxbuild3.err
cd /opt
===== end =====
any lines in first column are continuations of the one above... i'm sure
the cvs line will be broken into at least 3 lines and ./configure into 2
lines...
the above expects a copy of max-3.03-etc.tar.gz in the /opt directory...
the above is also done on a mandrake 7.1 (helium) system... there were some
large changes between v7, 8 and 9... the six log files of the process will
help... i actually have the portions from echo to echo in seperate scripts
so that i can run each manually and seperately if i need to for looking at
the logs between each stage...
my last successful pull, configure and compile was Nov 29, at about 10:30pm
eastern time...
)\/(ark
* Origin: (1:3634/12)SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.