Gabriel Dos Reis <[email protected]> writes:
> Aleksej Saushev <[email protected]> writes:
> | I used CVS ECL as of 28 Oct. Now I'm using last midnight UTC snapshot.
>
> OK; I know that around that timeframe, ECL was a bit unstable as it was
> being modified to support paths on cygwin and it took several iterations.
>
> | > | There's inconsistency about binary object files and Lisp fast load
> files,
> | > | I understand intention, but I don't know what exactly you want to
> achieve.
> | > | Probably, you want separate target for ECL, but I'm not sure.
> | >
> | > 'base-lisp' is a standalone application built from the bootstrapping
> | > Lisp, so , it must have $(EXEEXT) extension. So, I don't thinl that
> | > hunk of your proposed patch is correct.
> | >
> | > 'core.xxx' is a FASL produced, suitable for LOAD, so it is not
> | > technically a linkable object, so it must have the $(FASLEXT).
> | > Again, I don't believe the corresponding junk of your proposed patch is
> ^
> I meant "hunk" it came as 'junk' :-(
Not a problem, that was never meant a proper fix anyway.
> | > correct.
> |
> | Alright, I'll take a closer look.
> |
> | > Could you expand on the build failure you're seeing, and the platform
> | > you're using?
> |
> | gmake[2]: Entering directory `/tmp/wip/openaxiom/work/open-axiom/src/lisp'
> | gmake[2]: *** gmake[2]: Entering directory
> `/tmp/wip/openaxiom/work/open-axiom/src/hyper'
> | oa_enable_lisp_profiling= nil
> | No rule to make target `core.o', needed by
> `../../i486--netbsdelf/lisp/core.o'../../libtool --mode=compile cc -c -o
> addfile.o -O2 -mfpmath=sse -msse3 -march=nocona -finline-functions
> -fomit-frame-pointer -ffast-math -I/usr/pkg/include -O2 -Wall
> -I../../src/include -I../../config -I. addfile.c
> | . Stop.
> |
> |
> | Also, I see this:
> |
> | hthits.c: In function 'handleFile':
> | hthits.c:292: warning: format '%ld' expects type 'long int *', but argument
> 4 has type 'time_t *'
> | hthits.c:292: warning: format '%ld' expects type 'long int *', but argument
> 4 has type 'time_t *'
> |
> | And I think it is a bad idea, because of:
> |
> | #define _BSD_TIME_T_ __int64_t
>
> which is not a standard data type. What is the corresponding scanf format?
Probably the easiest way is using intmax_t ("%jd") or uintmax_t ("%ju")
and converting the input result.
--
HE CE3OH...
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
open-axiom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
