-------------- Original message from "Anton Ertl" 
<[email protected]>: --------
> > -------------- Original message from [email protected]: --------------
> > >My next problem is with C function calls. I am only defining one simple 
> > >call: 
> > > 
> > >c-function DeviceIoControl DeviceIoControl n n a n a n a a -- n 
> > > 
> > >This gives me the following errors: 
> > > > >Compiling RAM 19 13 12 
> > > > >/cygdrive/c/emacs/.gforth/libcc-tmp/gforth_c_7FCD27B4.c:1:32: 
> >gforth/0.7.0/libcc.h: No such file or directory 
> > 
> > >It looks like the reference to libcc.h is not being built properly. 
> > 
> > Now this is getting complicated. I found where to change it, in libcc.fs: 
> > 
> > \ s" #include " append ( c-addr u ) 
> > s" #include " ( c-addr u ) 
> > 2dup save-c-prefix-line drop free throw 
> > > I get the right thing when I make the system, but then when I make 
> > > install it 
> reverts back to: 
> > 
> > gforth/0.7.0/libcc.h 
> 
> That's strange, but anyway that's not the intended way to do it. The 
> intended way is to have the "/usr/local/include" in the include path 
> of the C compiler. I would actually expect that it would be there by 
> default, but in any case it should also be there explicitly. When you: 
> 
> see compile-wrapper-function1 
> 
> you should see somthing like: 
> 
> : compile-wrapper-function1 
> lib-handle 0= 
> IF c-source-file close-file throw 0 c-source-file-id ! s\" libtool --sile 
> nt --mode=compile gcc -I /usr/local/include" ... 
> ^^^^^^^^^^^^^^^^^^ 
> 
> and then gcc should find libcc.h just fine. 

Well, there's the problem:

see compile-wrapper-function1
: compile-wrapper-function1
  lib-handle 0=
  IF     c-source-file close-file throw 0 c-source-file-id ! s\" libtool --sile
         nt --mode=compile gcc -I /home/bernd/gforth/include" s\"  -O -c " s+

Now, to figure out how bernd got in there. ;)

DaR


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to