Juan Jose Garcia-Ripoll writes:
> Hopefully fixed in CVS. RENAME-FILE is all what you need -- even though the
> specification only mandates it should work for files and thus this assumption
> is not portable.
Is there any way to do it that would work in an already-released ECL?
Zach
--
Hopefully fixed in CVS. RENAME-FILE is all what you need -- even though the
specification only mandates it should work for files and thus this
assumption is not portable.
Juanjo
On Thu, Aug 19, 2010 at 8:26 PM, Zach Beane wrote:
> I'd like to rename a directory with ECL. If I have a directory l
I'd like to rename a directory with ECL. If I have a directory like
"/tmp/from/" and I want to rename it to "/tmp/to/", I get something like
this:
> (rename-file "/tmp/from/" "/tmp/to/")
Cannot rename the file "/tmp/from/" to #P"/tmp/to/".
Explanation: No such file or directory.
Is there a
On Thu, Aug 19, 2010 at 5:08 PM, Gabriel Dos Reis wrote:
> Where is the right place to put that CPP macro definition?
>
At the makefile in msvc. Those flags are then exported by a small program
(cut.exe) that rewrites certain files, doing the job of config.status.
Juanjo
--
Instituto de Físic
In fact I have a question I should ask now.
I am introducing a CPP macro, say ECL_MS_WINDOWS_HOST, that tells where
ECL is being built as a native Windows program (this includes using MS
compiler, GNU MinGW/MSYS or mingw-w64, but excludes Cygwin). This is
easily done by configure. And all is w
Juan Jose Garcia-Ripoll writes:
| BTW, I just finished configuring the Windows64 virtual image and right now all
| tests are run through it:
| http://ecls.sourceforge.net/logs.html
Great!
| However, I still have not managed installing mingw64, nor setting up the MSVC
| port to use LLP.
I wi
BTW, I just finished configuring the Windows64 virtual image and right now
all tests are run through it:
http://ecls.sourceforge.net/logs.html
However, I still have not managed installing mingw64, nor setting up the
MSVC port to use LLP.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Ser
Juan Jose Garcia-Ripoll writes:
[...]
| --with-dffi is only useful when combined with --enable-shared, because the
| later allows finding out shared libraries, loading them and retrieving
pointers
| to their C functions, which DFFI may then use as described before.
|
| --with-dffi is only need
On Thu, Aug 19, 2010 at 3:53 PM, Gabriel Dos Reis wrote:
> understand correctly, there might be two libffi floating around: one
> that ECL wants, and one that comes with GNU Compiler suite. [...]
> What is the relation between --enable-shared and --with-dffi?
>
--with-dffi is a feature that all
Juan Jose Garcia-Ripoll writes:
| On Wed, Aug 18, 2010 at 11:15 PM, Juan Jose Garcia-Ripoll <
| juanjose.garciarip...@googlemail.com> wrote:
|
| On Wed, Aug 18, 2010 at 6:37 PM, Gabriel Dos Reis
wrote:
|
| libeclmin.a(ffi.o): In function `si_make_dynamic_callback':
| c:/Do
On Wed, Aug 18, 2010 at 11:15 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@googlemail.com> wrote:
> On Wed, Aug 18, 2010 at 6:37 PM, Gabriel Dos Reis wrote:
>
>> libeclmin.a(ffi.o): In function `si_make_dynamic_callback':
>> c:/Docume~1/gdr/Desktop/ecl.cvs/src/c/ffi.d:976: undefined refer
11 matches
Mail list logo
