Re: System compilation failure, CLPPCRE, ASDF, SBCL involved

Holger Schauer <Holger.Schauer@xxxxxx> writes:

On 5293 September 1993, Juho Snellman wrote:
Holger Schauer <Holger.Schauer@xxxxxx> writes:
What baffles me is that I get that error only when I add the
parse-integer call. I don't understand that at all and also don't have
the slightest idea where to look next. Any hints?

PARSE-INTEGER needs a string argument. SBCL has noticed that there's a
chance it'd be called with NIL instead, and is giving a warning about
that. [...]
Or you can let SBCL know that YEAR will in fact not be NIL when
PARSE-INTEGER is called: (when year (parse-integer year))

Thanks. That indeed fixes both the warning and the error on ASDF
loading. While the problem at hand is now fixed, I would still be
interested to learn why a simple compilation warning may result in an
ASDF compile error. I would have thought that at the end of the day
all what ASDF does is to call compile-file. Usually warnings don't
result in errors during a load-op or compile-op, so is that also some
kind of SBCL special behaviour wrt. to type warnings or something?

Well, I don't know about ASDF, but I encountered something perhaps
similar when doing Loom development. What happened was that we had code
that called COMPILE and actually checked the second return value from
the COMPILE function to see if there were any problems. The style
warnings generated by CMUCL were enough to trigger this. (The code was
pre-ANSI and unfortunately, didn't check the third return value
instead...). Also, I think that some of the compiler notes were not
properly handled by COMPILE at one time, either.

Anyway, if there is some checking going on that tries to detect whether
a compilation succeeded or not, it could be affected by a compiler that
is somewhat pickier about the warnings that it issues.

COMPILE-FILE also returns three values, with the 2nd and 3rd
corresponding to WARNING-P and FAILURE-P, so this could be what is
triggering the ASDF behavior.

--
Thomas A. Russ, USC/Information Sciences Institute
.

Relevant Pages

  • RE: Redhat 9.0 development environment wierdness...
    ... It still has the warnings you posted. ... setup depends on you or the project you are trying to compile. ... Redhat 9.0 development environment wierdness... ... need to install on our servers and if I can't even get through these I ...
    (RedHat)
  • Re: does VS C++ 2005 actually work????
    ... may be the same size as a pointer, they have nothing logically to do with ... sizeofand size_t generating warnings when used in the context of API ... I can't compile ... justified criticism regarding the reliability of Windows. ...
    (microsoft.public.vc.mfc)
  • Re: 2.6.23.9-rt13
    ... If I compile -rt13 I get some compile warnings on ARM: ... Both warnings are fixed by the attached patch, but warning 2 needs some review. ... New changes by Steven Rostedt, Gregory Haskins, ... Revert lazy disable irq from simple irq handler ...
    (Linux-Kernel)
  • Re: Using unused variables
    ... I get loads of "unused variable" warnings during compile ... Compiler switches that disable reporting of unused variables are out of ... which may draw dead code diagnostics from aggressive optimizing compilers. ...
    (comp.lang.fortran)
  • Re: <ftream> errors under g++ 3.2.2
    ... > gives error messages about implicit typenames being deprecated, ... is nothing you can do to your code to prevent the warnings. ... From your output, I don't see compile failures, I see warnings. ... I am surprised that a GCC header would have an implicit ...
    (freebsd-current)