update fricas0-ecl and fricas0-data

[wangyenshu]

Template B: Checklist for updating a package

• ⚠️ Bump build number if the version remains unchanged
• Or reset build number to 0 if updating the package to a newer version

---

PR Formatting

• PR title follows format: Add [package-name] or Update [package-name] to [version]
• PR description includes:
  • Version being added/updated
  • Any special build considerations or patches applied

Package Details

• Package Name: fricas0-ecl, fricas0-data
• Version: various, see their recipe.yaml

Build Notes

This is a fix for fricas0-ecl and fricas0-data. The fricas0 compiled lisp code must match the architecture of wasm version of ecl. So the new recipe will build the 32bit host version of ecl and compile the lisp code. I have tested the local build.

[wangyenshu]

==> Running build script
Creating directory `build'
Switching to directory `build' to continue configuration.
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc -m32
checking whether the C compiler works... no
configure: error: in '$SRC_DIR/build':
configure: error: C compiler cannot create executables
See 'config.log' for more details

I am confused. The build works nicely on my machine. I checked the workflow file. It uses 64bit ubuntu. I need to build 32bit ecl on host before building wasm version of ecl.

If this cannot be fixed. I had to use the raw lisp file.

[IsabelParedes]

Suggested change

	- pkg-config
	- gcc
	- gxx

[IsabelParedes]

I am confused. The build works nicely on my machine.

On your machine it's likely using your system compilers.

From the config.log

cannot find libgcc_s.so.1: No such file or directory
cannot find -lgcc: No such file or directory

You probably need to point $LDFLAGS to the $BUILD_PREFIX

[wangyenshu]

Thanks. I updated $LDFLAGS. But it still says "checking whether the C compiler works... no". I tested again on my machine after block host gcc by alias. It works.

How do you get the config.log from github action? Maybe that will help.

[IsabelParedes]

An easy way is to add this to the failing command

<failed command> || cat config.log

You just need to check where the config log is if it's not in the current directory. But you could probably easily find it in your machine.

[wangyenshu]

I removed -m32 flag. It builds but it is 64bit ecl:

[81](https://github.com/emscripten-forge/recipes/actions/runs/29597319830/job/87940774604?pr=5950#step:7:1781)
Creating directory `build'
Switching to directory `build' to continue configuration.
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking how to run the C preprocessor... gcc -E
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for ranlib... (cached) ranlib
checking for ar... ar
checking for exctags... no
checking for ectags... no
checking for ctags... no
checking for etags... no
checking for emacs-etags... no
checking for ld flags when building shared libraries... -shared 
checking for required libraries... -ldl -lm
checking for architecture... X86_64
checking for software type... linux / 
checking whether to build the manual; finding install-info...... checking for install-info... /usr/bin/install-info
 install-info found.
checking for working makeinfo...... checking for makeinfo... /usr/bin/makeinfo
 Will build the manual.

[wangyenshu]

My mistake. Ecl need not to be 32bit. The version number of ecl that compiles fricas should be the same as the ecl that execute it. I guess now it should work.

[IsabelParedes]

Looks good. Thank you!