1. Still cannot compile 4.0
How do I compile 4.0 using watcom? I'm still getting errors like this.
Using openwatcom 1.7a.
compiling the front-end files...
compiling the back-end files...
linking all the files...
Warning! W1008: graph.lib cannot open : No such file or directory
Error! E2028: _16scientific_to_atom_ is a unspecified reference
Error! E2028: _20intoptions_ is a unspecified reference
Error! E2028: _21get_switches_ is a unspecified reference
File scanner.obj(J:\operasi\rapideuphoria\source\scanner.c):　unspecified
symbol _16scientific_to_atom_
File backend.obj(J:\operasi\rapideuphoria\source\backend.c):　unspecified
symbol _20intoptions_
File backend.obj(J:\operasi\rapideuphoria\source\backend.c):　unspecified
symbol _21get_switches_
2. Re: Still cannot compile 4.0
yuku wrote:
>
> How do I compile 4.0 using watcom? I'm still getting errors like this.
> Using openwatcom 1.7a.
>
> compiling the front-end files...
> compiling the back-end files...
> linking all the files...
> Warning! W1008: graph.lib cannot open : No such file or directory
> Error! E2028: _16scientific_to_atom_ is a unspecified reference
> Error! E2028: _20intoptions_ is a unspecified reference
> Error! E2028: _21get_switches_ is a unspecified reference
> File scanner.obj(J:\operasi\rapideuphoria\source\scanner.c):　unspecified
> symbol
> _16scientific_to_atom_
> File backend.obj(J:\operasi\rapideuphoria\source\backend.c):　unspecified
> symbol
> _20intoptions_
> File backend.obj(J:\operasi\rapideuphoria\source\backend.c):　unspecified
> symbol
> _21get_switches_
What did you type on the command line?
Matt
3. Re: Still cannot compile 4.0
Can you please do a svn up. Then change to the source directory and type:
wmake -f makefile.wat distclean
wmake -f makefile.wat
and see what happens.
--
Jeremy Cowgar
http://jeremy.cowgar.com
4. Re: Still cannot compile 4.0
- Posted by yuku <yuku at ikitek.??m>
May 05, 2008
-
Last edited May 06, 2008
Jeremy Cowgar wrote:
> Can you please do a svn up. Then change to the source directory and type:
>
> wmake -f makefile.wat distclean
> wmake -f makefile.wat
>
> and see what happens.
Looks good. But
wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
-DESIMPLE_MALLOC .\intobj\intinit.c -fo=.\intobj\intinit.obj
wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
-DESIMPLE_MALLOC .\intobj\symtab_0.c -fo=.\intobj\symtab_0.obj
wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
-DESIMPLE_MALLOC .\intobj\wildcard.c -fo=.\intobj\wildcard.obj
wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
-DESIMPLE_MALLOC .\intobj\sequence.c -fo=.\intobj\sequence.obj
Unable to open '.\intobj\sequence.c'
5. Re: Still cannot compile 4.0
- Posted by yuku <yuku at ik?t?k.com>
May 05, 2008
-
Last edited May 06, 2008
imakew.
But I have modified it to include /dEOW switch.
6. Re: Still cannot compile 4.0
- Posted by Jeremy Cowgar <jeremy at co?gar?com>
May 05, 2008
-
Last edited May 06, 2008
yuku wrote:
>
> Looks good. But
>
> wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> -DESIMPLE_MALLOC
> .\intobj\intinit.c -fo=.\intobj\intinit.obj
> wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> -DESIMPLE_MALLOC
> .\intobj\symtab_0.c -fo=.\intobj\symtab_0.obj
> wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> -DESIMPLE_MALLOC
> .\intobj\wildcard.c -fo=.\intobj\wildcard.obj
> wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> -DESIMPLE_MALLOC
> .\intobj\sequence.c -fo=.\intobj\sequence.obj
> Unable to open '.\intobj\sequence.c'
Can you get on IRC and we can work through this problem in real time?
--
Jeremy Cowgar
http://jeremy.cowgar.com
7. Re: Still cannot compile 4.0
Jeremy Cowgar wrote:
>
> yuku wrote:
> >
> > Looks good. But
> >
> > wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> > -DESIMPLE_MALLOC
> > .\intobj\intinit.c -fo=.\intobj\intinit.obj
> > wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> > -DESIMPLE_MALLOC
> > .\intobj\symtab_0.c -fo=.\intobj\symtab_0.obj
> > wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> > -DESIMPLE_MALLOC
> > .\intobj\wildcard.c -fo=.\intobj\wildcard.obj
> > wcc386 /bt=nt /mf /w0 /zq /j /zp4 /fp5 /fpi87 /5r /otimra /s
> > -DESIMPLE_MALLOC
> > .\intobj\sequence.c -fo=.\intobj\sequence.obj
> > Unable to open '.\intobj\sequence.c'
>
> Can you get on IRC and we can work through this problem in real time?
>
> --
> Jeremy Cowgar
> <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a>
Was this ever resolved? I am having the same issue.
8. Re: Still cannot compile 4.0
Mike Sywensky wrote:
> Was this ever resolved? I am having the same issue.
Yes, however... Right this instant, Matt and I are adding regular expression
support and trunk is a tad unstable. So depending on when you last did a svn up,
it may/may not work.
We do our very best to leave the repo in a working state, but this was a rather
large addition w/some build changes on multiple platforms. I will let you know
when the repo is stable again. It shouldn't be too long.
Now, if you have not updated since about May 6, 10PM EST, then your probably OK.
I wrote a tutorial on compiling 4.0 on the wiki and posted the link here:
http://www.openeuphoria.org/EUforum/m20544.html
--
Jeremy Cowgar
http://jeremy.cowgar.com
9. Re: Still cannot compile 4.0
Mike Sywensky wrote:
>
> Was this ever resolved? I am having the same issue.
How are you trying to build it? Please specify exactly what you're typing
at the command line.
Matt
10. Re: Still cannot compile 4.0
Matt Lewis wrote:
>
> Mike Sywensky wrote:
> >
> > Was this ever resolved? I am having the same issue.
>
> How are you trying to build it? Please specify exactly what you're typing
> at the command line.
>
> Matt
I used the tutorial that Jeremy wrote, so I typed wmake -f makefile.wat at the
command line.
It is installed on my home machine, so I can't troubleshoot until I go home
tonight.
11. Re: Still cannot compile 4.0
Mike Sywensky wrote:
>
> I used the tutorial that Jeremy wrote, so I typed wmake -f makefile.wat at the
> command line.
>
> It is installed on my home machine, so I can't troubleshoot until I go home
> tonight.
Key things are: Make sure eu-3.1 is in your path. Make sure EUDIR is pointing to
your new eu-4.0 install. If you previously tried to build with an incorrect
EUDIR, then it's very possible that files were generated from your 3.1's include
directory, which will not work when compiling 4.0.
To remedy this problem, run wmake -f makefile.wat distclean ... I found out on
IRC that distclean does not work on Windows 98 or 95 due do rmdir missing a /S
switch. If you are on Windows 98 or 95, please remove these directories manually
from the source directory: backobj, intobj, libobj and transobj. This will clear
all generated .c file.
If you still have problems, I can try to help in real time on irc.
(irc.freenode.net #euphoria).
--
Jeremy Cowgar
http://jeremy.cowgar.com
12. Re: Still cannot compile 4.0
> We do our very best to leave the repo in a working state, but this was a
> rather
> large addition w/some build changes on multiple platforms. I will let you know
> when the repo is stable again. It shouldn't be too long.
>
It's compilable again.
--
Jeremy Cowgar
http://jeremy.cowgar.com
