> The way we solved this problem on our system is creating a compiler wrapper.
> This is a non-pypy-specific solution, which we believe is very effective and
> convenient.
>
> The "normal" gcc is installed in non-standard out-of-path location. A gcc
> shell script is installed instead. Such a script will call the actual gcc
> with all the proper -I -L -l of the other libraries (managed by lmod). In
> fact, in this way, it's a piece of cake to maintain several versions of the
> same library (and compiler and everything) on the system.
>
> I can elaborate more if this is not clear.
I thought it was clear, but my initial attempts at a wrapper have yielded no
improvement. Here's what my wrapper looks like at the moment:
#!/bin/bash
# Wrapper around GCC used to add a number of non-standard library and
# include file locations to command lines when building pypy.
gcc \
-L/opt/TWWfsw/ncurses57/lib -I/opt/TWWfsw/ncurses57/include \
-I/opt/TWWfsw/ncurses57/include/ncurses \
"$@"
This seems to me what you were describing, and in fact, I've verified that
at curses.h and term.h exist in the second -I directory. Lots of other compile
commands before the failure succeed, and do use my minimal gcc-wrap
script, so I'm sure it's being invoked, and doesn't have some stupid bug like
a syntax error or typo.
Hints appreciated...
Thx,
Skip
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
