Greetings, and thanks for your report! I've just upgraded to gcc-4.0 on my Debian unstable dchroot, and made a few patches against the next upstream release version 2.6.7 to address the new warnings. Am testing now, and if all is OK with maxima, acl2 and axiom, will release 2.6.7 and a new Debian package for it. I do not see the effects you describe below. I'm hoping that as ubuntu stays fairly close to Debian that you won't either once the upload is made. If you want, I can show you how to get the pre-release from cvs.
Last call for interested parties to suggest anything that should go into 2.6.7 beyond what is in the -pre branch now. Bill? Tim? Mike has given the go ahead as gcl-tk on Windows will take a bit more time. Take care, Jorge Daza <[EMAIL PROTECTED]> writes: > Hello, > > I'm trying to build a debian package for ubuntu with gcl-2.6.6, we're > in the middle of the gcc-4.0 transition, so we're rebuilding packages. > > gcl gave several errors regarding static functions that were solved, > but later in the build process, when it starts compiling .lsp files it > starts giving errors without stoping. At the end, at linking time, > there are several unresolved symbols. > > The errors that the lsp compiler gives are like this: > > ------------------------------------->cut<----------------------------------- > Compiling gcl_defstruct.lsp. > Loading ./gcl_cmpinit.lsp > Loading sys-proclaim.lisp > Finished loading sys-proclaim.lisp > Finished loading ./gcl_cmpinit.lsp > Warning: DEFSTRUCT is being redefined. > Warning: not replacing s-data property > End of Pass 1. > > Error: Someone tried to RETURN-FROM a TAGBODY. > Error signalled by LET. > Backtrace: gcl-top-level > if > let > setq > error-set > error-set > > progn > compile-file > loop > setq > apply > apply > > compiler::compile-file1 > let > unwind-protect > progn > let* > let > > unwind-protect > progn > when > compiler::compiler-pass2 > let > > unwind-protect > progn > let > let > unwind-protect > progn > catch > > compiler::ctop-write > do* > when > apply > apply > compiler::t3defun > > cond > compiler::analyze-regs > let > cond > let > > compiler::analyze-regs1 > let > tagbody > universal-error-handler > > let > let > cond > apply > apply > universal-error-handler > > break-level > let* > UNLESS > In file included from gcl_defstruct.c:3: > gcl_defstruct.h:3:19: warning: no newline at end of file > gcl_defstruct.c: In function 'init_gcl_defstruct': > gcl_defstruct.c:4: error: 'VV' undeclared (first use in this function) > gcl_defstruct.c:4: error: (Each undeclared identifier is reported only once > gcl_defstruct.c:4: error: for each function it appears in.) > gcl_defstruct.c:4:40: warning: no newline at end of file > ------------------------------------->cut<----------------------------------- > > Do you know why could this be happening ? > > Thanks in advance, > > Jorge > > > _______________________________________________ > Gcl-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/gcl-devel > > > -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gcl-devel
