Re: [Chicken-hackers] [ANN]: Port Chicken to AIX

[Erik Falor]

On Tue, Aug 13, 2013 at 09:08:02PM +0200, Peter Bex wrote:
> - Why is stty not compiling?  NetBSD also doesn't have ncurses as
>    native curses library, but stty works there anyway.  AFAIK it doesn't
>    link against curses nor use its header files, it just does some ioctls.

* I've revisited the stty egg.  Here's the output from chicken-install:

  % chicken-install -n
  retrieving ...
  checking platform for `stty' ...
  checking dependencies for `stty' ...
  install order:
  ("stty")
  installing stty: ...
  changing current directory to .
    '/home/efalor/.storm-dev/bin/csi' -bnq -setup-mode -e "(require-library 
setup-api)" -e "(import setup-api)" -e "(setup-error-handling)" -e 
"(extension-name-and-version '(\"stty\" \"\"))" -e "(keep-intermediates #t)" -e 
"(setup-install-mode #f)" 'stty.setup'
    '/home/efalor/.storm-dev/bin/csc' -feature compiling-extension -setup-mode 
-k   -shared -O2 -j stty stty.scm
  stty.c: In function 'stub178':
  stty.c:93: error: 'struct_termios' has no member named 'c_ospeed'
  stty.c: In function 'stub169':
  stty.c:104: error: 'struct_termios' has no member named 'c_ospeed'
  stty.c: In function 'stub160':
  stty.c:116: error: 'struct_termios' has no member named 'c_ispeed'
  stty.c: In function 'stub151':
  stty.c:127: error: 'struct_termios' has no member named 'c_ispeed'
  stty.c: In function 'f_978':
  stty.c:1734: error: 'VWERASE' undeclared (first use in this function)
  stty.c:1734: error: (Each undeclared identifier is reported only once
  stty.c:1734: error: for each function it appears in.)
  stty.c:1747: error: 'CRTSCTS' undeclared (first use in this function)

  As I said before, I'm not conversant with curses nor terminals.  I'm
  sure it won't be much trouble to fix this egg - it's probably just a
  matter of some #ifdefs to work around differently-named symbols in
  IBM's termios.h.

* In other news, I'm making (slow) progress in getting `make check` to
  work.  I was finally able to solve the problem with the 'private
  repository' test by letting AIX use the vanilla branch of Unix code in
  chicken.h's C_path_to_executable().  I tried a few platform-specific
  methods of determining that information, but it seems that AIX's /proc
  just doesn't keep track of the full path of a running image.

* `make check` now fails on the final "deployment tests" in runtests.sh,
  which I'm working on now.
  The final test builds a little program called rev-app/rev-app under
  the tests/ directory.  That program fails to run because it cannot
  find libchicken.so.

* I also figured out what I did wrong in Makefile.aix that led me to
  hardcoding AIX-specific linker flags into csc.scm.  I didn't specify
  a value for the Make variable LINKER_OPTIONS, so that info wasn't
  propagated into the csc program.

* While inspecting the code I put into Makefile.aix, I went through
  all of the #defines that are echoed into chicken-config.h, making
  sure that they are correct for my platform.  I notice that while
  these macros are present in chicken-config.h, they don't seem to be
  referenced by Chicken itself.  Are they there as insurance against
  the future, or are they leftover cruft from versions gone by?

-- 
Erik Falor                                       http://unnovative.net
Registered Linux User #445632                  http://linuxcounter.net

signature.asc
Description: Digital signature