On Mon, 14 Jan 2008, Camm Maguire wrote:
I believe the issue here is that the collectfn.o module has been
stripped. GCL appends initialization data to its compiled object
modules by default -- if missing, then .data files are sought. GCL
itself installs the .o file alone, and typically package installers
run strip on such objects unless instructed to do otherwise.
I suppose you are right. This ebuild, probably, strips .o files. I'll
insert a line which forbids this action.
The weird path results from the si::*load-path* order:
si::*load-path*
("/usr/lib/gcl-2.6.8/xgcl-2/" "/usr/lib/gcl-2.6.8/lsp/"
"/usr/lib/gcl-2.6.8/gcl-tk/" "/usr/lib/gcl-2.6.8/cmpnew/")
This is harmless, AFAICT.
Yes, it is harmless, of course.
Many thanks,
Andrey
_______________________________________________
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
