I know that the man behind lparser released the C source to it, but it
won't appear to compile without work in the code (which I don't know how
to do yet). So, I was wondering if anyone was able to port it to linux,
and knew where I could get it?

That's about it, thanks for the help, and happy tracing
Tim Soderstrom
TigerHawk

Post a reply to this message

TigerHawk wrote:
> 
> I know that the man behind lparser released the C source to it, but it
> won't appear to compile without work in the code (which I don't know how
> to do yet). So, I was wondering if anyone was able to port it to linux,
> and knew where I could get it?
> 
> That's about it, thanks for the help, and happy tracing
> Tim Soderstrom
> TigerHawk

That very easy!
You just compile the raw source code from Laurens's webpage. Make sure
you add -lm to compiling options. I learned it the hard way! :-)

If you still have any problems I can send you one from home.

All the Best,

Marc
-- 
Marc Schimmler

Post a reply to this message

Well, I tried to compile it and got this (see bottom).
(it's been cut, but it repeats alot, so I think you get the general idea)
I just don't quite know what's wrong. I tried it with gcc-2.7.2.1 and egcs.
In any case, if you could send me your compiled binary, I would apreciate it!

Thanks for the help!

Tim Soderstrom
TigerHawk


(Output snippet)
LPARSER.C:246: stray '\' in program
LPARSER.C:247: syntax error before `*='
LPARSER.C:247: stray '\' in program
LPARSER.C:248: syntax error before `*='
LPARSER.C:248: stray '\' in program
LPARSER.C: In function `void Set_ECS(float *)':
LPARSER.C:1459: stray '\' in program
LPARSER.C:1462: stray '\' in program
LPARSER.C:1463: parse error before `else'
LPARSER.C:1464: stray '\' in program
LPARSER.C:1467: stray '\' in program
LPARSER.C:1468: stray '\' in program
LPARSER.C:1469: stray '\' in program
LPARSER.C:1475: cannot declare static function inside another function
LPARSER.C:1475: parse error before `{'
LPARSER.C:1477: `p2' undeclared (first use this function)
LPARSER.C:1477: (Each undeclared identifier is reported only once
LPARSER.C:1477: for each function it appears in.)
LPARSER.C:1477: `p1' undeclared (first use this function)
LPARSER.C:1477: confused by earlier errors, bailing out

Post a reply to this message

TigerHawk wrote:
> 
> Well, I tried to compile it and got this (see bottom).
> (it's been cut, but it repeats alot, so I think you get the general idea)
> I just don't quite know what's wrong. I tried it with gcc-2.7.2.1 and egcs.
> In any case, if you could send me your compiled binary, I would apreciate it!
> 
> Thanks for the help!
> 
> Tim Soderstrom
> TigerHawk
> 
> (Output snippet)
> LPARSER.C:246: stray '\' in program
> LPARSER.C:247: syntax error before `*='
> LPARSER.C:247: stray '\' in program
> LPARSER.C:248: syntax error before `*='
> LPARSER.C:248: stray '\' in program
> LPARSER.C: In function `void Set_ECS(float *)':
> LPARSER.C:1459: stray '\' in program
> LPARSER.C:1462: stray '\' in program
> LPARSER.C:1463: parse error before `else'
> LPARSER.C:1464: stray '\' in program
> LPARSER.C:1467: stray '\' in program
> LPARSER.C:1468: stray '\' in program
> LPARSER.C:1469: stray '\' in program
> LPARSER.C:1475: cannot declare static function inside another function
> LPARSER.C:1475: parse error before `{'
> LPARSER.C:1477: `p2' undeclared (first use this function)
> LPARSER.C:1477: (Each undeclared identifier is reported only once
> LPARSER.C:1477: for each function it appears in.)
> LPARSER.C:1477: `p1' undeclared (first use this function)
> LPARSER.C:1477: confused by earlier errors, bailing out


Have you removed the additional CRs (?) at the end of the lines? The
source has been written under M$. I remember GCC having problems with
that not giving clear messages. I'll have a look and send you the
binaries anyway.

All the Best,

Marc 
-- 
Marc Schimmler

Post a reply to this message

TigerHawk wrote:
> 
> Well, I tried to compile it and got this (see bottom).
> (it's been cut, but it repeats alot, so I think you get the general idea)
> I just don't quite know what's wrong. I tried it with gcc-2.7.2.1 and egcs.
> In any case, if you could send me your compiled binary, I would apreciate it!
> 
> Thanks for the help!
> 
> Tim Soderstrom
> TigerHawk
> 

Couldn't get through to your email! My server reports a failure at your
side :-(
Please contact me!

Marc
-- 
Marc Schimmler

Post a reply to this message

Eh? Really? It should be Tig### [at] SticNet (maybe w/o caps, but I doubt it's case
sensetive anyway. UHmm...hmm..that's odd...I didn't know i had to modify the
source though, I guess I can try that. YOu might want to try it again though, it
was up when I checked my mail - most people sending get to it no problem....

No worries,
Tim Soderstrom
TigerHawk

Post a reply to this message

TigerHawk wrote:
> 
> Eh? Really? It should be Tig### [at] SticNet (maybe w/o caps, but I doubt it's case
> sensetive anyway. UHmm...hmm..that's odd...I didn't know i had to modify the
> source though, I guess I can try that. YOu might want to try it again though, it
> was up when I checked my mail - most people sending get to it no problem....
> 
> No worries,
> Tim Soderstrom
> TigerHawk

I tried it this time with the caps but it says:

**********************************************************

The original message was received at Tue, 6 Jul 1999 03:09:15 -0400
from roo### [at] charybdisrusuni-stuttgartde [129.69.1.58]

   ----- The following addresses had permanent fatal errors -----
<Tig### [at] SitcNet>

   ----- Transcript of session follows -----
554 MX list for sitc.net. points back to wolverine.emji.net

Reporting-MTA: dns; wolverine.emji.net
Received-From-MTA: DNS; charybdis.rus.uni-stuttgart.de
Arrival-Date: Tue, 6 Jul 1999 03:09:15 -0400

Final-Recipient: RFC822; Tig### [at] SitcNet
Action: failed
Status: 5.5.0
Remote-MTA: DNS; sitc.net
Last-Attempt-Date: Tue, 6 Jul 1999 03:11:24 -0400

***************************************************************

Sorry!

Marc
-- 
Marc Schimmler

Post a reply to this message

On Tue, 06 Jul 1999 09:17:01 +0200, Marc Schimmler
<sch### [at] icauni-stuttgartde> wrote:

>   ----- The following addresses had permanent fatal errors -----
><Tig### [at] SitcNet>

  Hi, Marc. Look again at Tim Soderstrom's previous post (different in the
"From" line and the body of his message), paying special attention to the
spelling of the domain. He spells it "s t i c", but you have it as "s i t
c". What happens if you try it with the revised spelling?

-- 
Alan
--------------------------------------------------------------------
http://www.povray.org - Home of the Persistence of Vision Ray Tracer
news.povray.org - where POV-Ray enthusiasts around the world can get
together to exchange ideas, information, and experiences with others
--------------------------------------------------------------------

Post a reply to this message

Alan Kong wrote:
> 
> On Tue, 06 Jul 1999 09:17:01 +0200, Marc Schimmler
> <sch### [at] icauni-stuttgartde> wrote:
> 
> >   ----- The following addresses had permanent fatal errors -----
> ><Tig### [at] SitcNet>
> 
>   Hi, Marc. Look again at Tim Soderstrom's previous post (different in the
> "From" line and the body of his message), paying special attention to the
> spelling of the domain. He spells it "s t i c", but you have it as "s i t
> c". What happens if you try it with the revised spelling?
> 
> --
> Alan

Hi Alan!

Your are right! Lazy me tried to use reply to sender with the email
address given in the header! This one is spelled wrong!
I changed it and it worked (at least I did not get an error). Thank you
very much and Tim ... please correct your email address in your browser!

Thanks,

Marc
--
Marc Schimmler

Post a reply to this message

My e-mail addresss is wrong? tig### [at] sticnet is what it should be for a mail
reply....

Tim Soderstrom
TigerHawk

Post a reply to this message