Greetings, and thanks so much for your feedback! I am about to commit a fix for most if not all your prototype warnings. This should help clarify the logs. Am reading the rest for other signs...
There have been an number of fixes committed in supporting the other Debian architectures -- you might want to retry. I do think the Sonoma access is probably the most efficient way to go from here. Take care, "Chun Tian (binghe)" <binghe.l...@gmail.com> writes: > Greetings, > > Please find in attach three log files. My GCC (clang) information is the > following (Note that it's impossible to get more info like 'gcc -v' with > a real GCC compiler): > > binghe@binghe-mac7:~/Lisp/gcl/gcl$ gcc -v > Apple clang version 15.0.0 (clang-1500.1.0.2.5) > Target: x86_64-apple-darwin23.3.0 > Thread model: posix > InstalledDir: > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin > > The "configure.log" is generated by the following commands in GCL > working directory (with the unmodified 'master', commit id: 22c93c4c) > > export C_INCLUDE_PATH=/opt/local/include > export LIBRARY_PATH=/opt/local/lib > > ./configure --prefix=/usr/local \ > --disable-notify \ > --disable-statsysbfd \ > --disable-ansi \ > --enable-custreloc \ > --enable-emacsdir=/opt/local/share/emacs/site-lisp/gcl \ > --enable-infodir=/opt/local/share/info \ > --enable-readline \ > --disable-gprof \ > --without-x \ > --disable-xgcl \ > --disable-tcltk \ > --enable-dynsysgmp \ > --enable-debug > configure.log > > Then I found there's another "config.log" with more information (about > my building environment), so I attached it too. (The file is 4MB big, so > I compressed it by bzip2). > > Then I call make and redirected all std and error outputs to "make.log": > > binghe@binghe-mac7:~/Lisp/gcl/gcl$ make >& make.log > > The building process stopped at the previous mentioned linking issue > "symbol not found in flat namespace '_Cnil_body'". > > Unfortunately, I can't see any special compiler warnings about the > fixnum/ufixnum issue. More importantly, the previous observed crash > disappeared, even without your proposed code changes! (I think this > means the crashing is sensitive to particular memory layout, or due to > memory leaking, thus not always reproducible.) > > Hope this helps... > > P.S. I think I can provide you a remote access to a macOS Sonoma virtual > machine that you can connect to its desktop by VNC. (We can talk more > about this in private communications.) > > Chun -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
