Greetings, and thanks for the report! Actually, the output should have also included the symbol name, unless stderr was redirected somewhere else.
This is almost always due to compiling GCL with one C compiler and set of flags, and then using another combo when using GCL as a compiler. Most gcc flags (as in compiler::*cc*) are completely benign, but some (like stack-protector), compile in symbols which are not present otherwise. GCL needs to know about these from the start. Can you find the symbol name? Does it sound like something like the above is going on? Take care, Robert Dodier <[email protected]> writes: > For the record, gcl --version reports: GCL 2.7.1 git tag Version_2_7_2pre15 > > Looks like the Maxima build process failed early on, but I guess GCL > did not exit with nonzero status, so defsystem kept plugging along, > and an executable is dumped which contains the small amount of stuff > that was successfully processed. > > The error message is: > > ; - Compiling module "intl" > ; - Loading binary file "binary-gcl/intl.o" > Condition in PROGN [or a callee]: INTERNAL-SIMPLE-ERROR: The assertion > !emsg("Unrelocated non-local symbol: %s\n",st1+sym->st_name) on line > 248 of o/sfaslelf.c in function relocate_symbols failed: Success > > Broken at FUNCALL. Type :H for Help. > 1 Return to top level. > > Any advice is welcome. > > Robert -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
