Alexander Hansen wrote:
[]
> It looks like the problem isn't due to sed, but rather to the "echo" 
> command on 10.5.  I guess I never built the package there.  I'm not sure 
> exactly to look for to patch out, though.  Here are the references that 
> include both echo and sed in configure, and if anybody has a 
> prescription for what to fix, I'd appreciate it.

I haven't looked at this on 10.4, so I don't know why it works there, 
but on 10.5, the problem comes from the fact that the command

  fltk-config --use-gl --libs

gives a 2-line response instead of one line. Whether this is to be 
considered a bug in fltk-aqua, I don't know, but it makes the oct-plot 
configure phase do crazy things. Fixing it in fltk-aqua could perhaps be 
done by replacing some 'echo' commands by 'printf', but the fltk-config 
script employs some complicated logic, so this would need careful 
checking. It looks easier to work around this in octplot.

The following patch line in octplot-10.5.info makes the build go through 
for me:

perl -pi -e "s,use-gl --libs,use-gl --libs | tr \'\\\n\' \' \'," configure

(in one line)

This replaces the line break in the output by a space. It is equivalent 
to the patch file

--- configure.bak       2007-04-24 19:33:09.000000000 +0200
+++ configure   2008-09-10 10:10:57.000000000 +0200
@@ -4813 +4813 @@
-    LIBS="$LIBS `$FLTK_CONFIG $fltkconf_args --use-gl --libs`"
+    LIBS="$LIBS `$FLTK_CONFIG $fltkconf_args --use-gl --libs | tr '\n' 
' '`"

(last line in one line)

-- 
Martin



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to