On Thu, Jul 05, 2007, Ralf S. Engelschall wrote:
On Thu, Jul 05, 2007, Christoph Schug wrote:
upgrading package: swig 1.3.29 - 1.3.31
Sorry, every version since 1.3.29 breaks for me under FreeBSD.
You can see it on rm0.openpkg.net:
| checking for Guile header files... /openpkg-dev/include
| checking for Guile library... checking whether Guile's gh_ API works... no
| checking whether Guile's SCM_ API works... no
| ./configure: line 7487: syntax error near unexpected token `('
| ./configure: line 7487: ` RUBYDIR=`($RUBY -rmkmf -e 'print
Config::CONFIG[archdir] || $archdir') 2/dev/null`'
| error: Bad exit status from /tmp/rse/openpkg/rpm-tmp.54670 (%build)
I've already looked at this once, but was not able to figure out
immediately a solution. Can you investigate on this?
Had similar problem, too. Nevertheless, this is not related to swig
1.3.31, it also happens to 1.3.29 when you try to compile it on the
same environment. The error message itself is misleading, since the
error is triggered several lines above in the configure script. For me,
it looks more like a bug of the shell since I haven't found any syntax
errors (correct me if I'm wrong). In your case your shell most likely
misinterprets the hash signs in following snippet as comment, leaving
the backticks unbalanced. The next backtick is down in the Ruby section,
thus resulting in the error you see above.
snippet from ./configure
[...]
| if test -n $MZSCHEME; then
| echo $as_me:$LINENO: checking for MzScheme dynext object 5
| echo $ECHO_N checking for MzScheme dynext object... $ECHO_C 6
| MZDYNOBJ=`$MZSCHEME --mute-banner --version --eval '(begin (require (lib
link.ss dynext)) (with-handlers (((lambda args #t) (lambda args #f)))
(for-each (lambda (x) (display x) (display ))
((current-make-standard-link-libraries (with-handlers (((lambda args #t)
(lambda args #f))) (for-each (lambda (x) (display x) (display ))
(expand-for-link-variant (current-standard-link-libraries)'`
| echo $as_me:$LINENO: result: $MZDYNOBJ 5
| echo ${ECHO_T}$MZDYNOBJ 6
| fi
[...]
Til now, I wasn't able to hunt down the root cause, but I'm sure it
hasn't anything to do with swig itself. Looks more like a bug in bash to
me. In my environment (and several others I've got at hand) it builds
like a charm. I already played around with several patch levels of GNU
bash, but as mentioned, I wasn't able to nail down the root cause yet.
-cs
__
OpenPKG http://openpkg.org
Developer Communication List openpkg-dev@openpkg.org
