gforth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gforth] Latest git and cygwin 64-bit


From: Dennis Ruffer
Subject: Re: [gforth] Latest git and cygwin 64-bit
Date: Tue, 13 Aug 2013 14:06:52 -0700

From: Bernd Paysan [mailto:address@hidden 
Sent: Tuesday, August 13, 2013 12:51 PM
Am Dienstag, 13. August 2013, 12:28:30 schrieb Dennis Ruffer:
> You wrote: " To solve the chicken and egg problem do a make dist e.g. 
> on Linux and untar the created tarball on cygwin64."
> 
> I'm not sure exactly what that gained, but the build did get further.  
> It still fails, with log attached. ;(
> 
> I see that you commented out the thread affinity and the 32 bit 
> compile appears to get as far as it used to, but the make install still
fails:
> 
> $ make install
> cp -p kernl32l.fi kernl32l.fi~
> cp -p kernl32l.fi- kernl32l.fi
> ./gforthker -p ".:~+:." etags.fs except.fs startup.fs fflib.fs cstr.fs 
> unix/socket.fs unix/pthread.fs unix/mmap.fs unix/serial.fs -e bye 
> redefined field,
> *** Warning: This system can not link to static lib archive 
> /usr/lib/libavcall.la.
> *** I have the capability to make that library automatically link in 
> when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.
> *** But as you try to build a module library, libtool will still 
> create
> *** a static module, that should work as long as the dlopening 
> application
> *** is linked with the -dlopen flag to resolve symbols at runtime.
> 
> file not found
> uncaught exception: error #-2
> Makefile:975: recipe for target `gforth.TAGS' failed
> make: *** [gforth.TAGS] Error 2

It looks like the check on ffcall succeeds, but you don't have the necessary
dynamic libraries for it to build successfully.  Go to the Makefile and edit
ffcall.fs out in the LIBCC_SRC variable.

<DaR> The LIBCC_BUILD_SRC variable had fflib.fs in the 04/09 version (which
works) but it wasn't used in gforth.TAGS.

<DaR> I've got libtool and ffcall, but no /usr/lib or libavcall*.  Why was
that change made?

<DaR> Any more clues on the 64 bit version?

DaR

--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]