you are probably running your tests in your default 'bash'
environment. The script runs in its own 'sh' environment, which is
most likely somewhat different.
Try the test in a test.sh script with #!/bin/sh at the top.
.hc
On Apr 11, 2008, at 11:12 AM, marius schebella wrote:
> I cannot confirm that:
>
> echo -e marius\\nhans
> prints out
>
> marius
> hans
>
> as expected.
> but maybe the problem is that
> ECHO = echo
> prints out
> = echo
> marius.
>
> Hans-Christoph Steiner wrote:
>> It's actually, the "-e" option to 'echo', which means "interpret
>> extended syntax", like "\n". Not all 'echo's support it. Your
>> 'echo' does not, it just echos the "-e" and "\n" unchanged.
>> Basically, someone needs to rewrite that chunk to not rely on a
>> specific version of 'echo'. I think it could be done with 'sed'
>> easily, or perhaps 'printf', if anyone wants to give it a shot.
>> .hc
>> On Apr 10, 2008, at 9:05 PM, marius schebella wrote:
>>> I think the toxy error results from some sed problem, in
>>> particular the "-e" option of sed. sed seems to write a strange
>>> line into setup.wiq if I open it, the first line starts like
>>>
>>> -e // Do not edit this file (edit "../test/toxy/setup.wid", and
>>> run "make").\n//\nputs stderr [concat loading built-in widget
>>> definitions]
>>> package provide toxywidgets 0.1.0.17
>>>
>>> i am not a frequent sed user, and I also don't know what the
>>> makefile hack means, I think, hans, you added that, maybe for
>>> 10.5 it needs a special treatment:
>>>
>>> ROOT_DIR = ..
>>> WIDPATH = $(ROOT_DIR)/test/toxy/setup.wid
>>> WIQFILE = $(notdir $(WIDPATH:.wid=.wiq))
>>> # this is necessary to deal with cross-platform echo issues with
>>> '-e'
>>> ifeq ($(shell echo -e|sed 's|^-||'),e) ECHO = /bin/echo
>>> else
>>> ECHO = echo
>>> endif
>>> redefault: checkwiq $(WIQFILE) default
>>> checkwiq:
>>> @if [ -f $(WIQFILE) ] && ! [ -s $(WIQFILE) ] ; then \
>>> echo ERROR: empty file $(WIQFILE)... removed ; \
>>> rm -f $(WIQFILE) ; fi
>>> $(WIQFILE): $(WIDPATH)
>>> @echo transferring widget definitions from \"$<\" to \"[EMAIL
>>> PROTECTED]"
>>> # LATER think how to replace puts with pdtk_post
>>> $(ECHO) -e '// Do not edit this file (edit "$<", and run
>>> "make").\n//\nputs stderr [concat loading built-in widget
>>> definitions]' \
>>> | cat - $< | sed \
>>> -e '1,\|//$$|{p;d;}' \
>>> -e 's/\([\\\"]\)/\\\1/g' \
>>> -e 's/^.*$$/\"&\\n\"/' > $@
>>> @if [ -f $(WIQFILE) ] && ! [ -s $(WIQFILE) ] ; then \
>>> echo ERROR: transfer failed... $(WIQFILE) removed ; \
>>> rm -f $(WIQFILE) ; fi
>>> include $(ROOT_DIR)/Makefile.common
>>>
>>> marius.
>>>
>>> Hans-Christoph Steiner wrote:
>>>> 10.4 builds work on 10.5 fine, as far as I know. Are you
>>>> having problems building or using binaries? Yes, Fink is not
>>>> perfect, but imagine trying to build all that stuff by hand...
>>>> and then write up instructions for someone else to do it...
>>>> shudder...
>>>> - My FTGL update has be included in Fink, so no need for the
>>>> manual file install:
>>>> http://pdb.finkproject.org/pdb/package.php/libftgl1
>>>> - I haven't run into the ptex-nox-base problem myself, I
>>>> generally try installing all of the dependencies from 'stable',
>>>> then switch to 'unstable' for the rest. If an 'unstable'
>>>> package adds more dependencies, then I switch back to 'stable'
>>>> and try building them all there, then switch back to 'unstable'
>>>> to finish everything. It may sound complicated, but it is not
>>>> really. It is just some copy-n- pasting of package names, and
>>>> running 'fink configure' a few times.
>>>> - the toxy build problem is the classic 'nifty hack' issue,
>>>> where the dev stuck some write-only code in the Makefile as a
>>>> quick hack to get things working, then built the library upon
>>>> that hack...
>>>> .hc
>>>> On Apr 10, 2008, at 4:03 AM, David Plans Casal wrote:
>>>>> On 10 Apr 2008, at 01:35, bsoisoi wrote:
>>>>>
>>>>>> are you on 10.5? Welcome to the mac os x pd-extended nightmare
>>>>> Hear hear. 10.5 build is becoming the first reason in ten years
>>>>> I've
>>>>> looked for another dev platform than pd. Mind, I think maybe a
>>>>> switch
>>>>> back to old Linux is a better option.
>>>>>
>>>>> David
>>>>>
>>>>>> !B
>>>>>>
>>>>>>
>>>>>> On Apr 9, 2008, at 7:52 PM, marius schebella wrote:
>>>>>>
>>>>>>> tried fink install coreutils-default and...
>>>>>>> ... then I tried fink install sed and...
>>>>>>> ... then it did not work still.
>>>>>>> marius.
>>>>>>>
>>>>>>>
>>>>>>> Hans-Christoph Steiner wrote:
>>>>>>>> Arg, this bug again. There is some crazy scripting in this
>>>>>>>> makefile, it
>>>>>>>> is quite problematic:
>>>>>>>>
>>>>>>>> http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/
>>>>>>>> externals/miXed/toxy/Makefile
>>>>>>>>
>>>>>>>>
>>>>>>>> .hc
>>>>>>>>
>>>>>>>> On Apr 9, 2008, at 6:22 PM, marius schebella wrote:
>>>>>>>>> hi,
>>>>>>>>> trying to build an intel build of pd-extended and get an
>>>>>>>>> error for
>>>>>>>>> toxy,
>>>>>>>>> don't know what is wrong. thanks,
>>>>>>>>> marius.
>>>>>>>>>
>>>>>>>>> gcc -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses
>>>>>>>>> -Wno-switch -march=pentium4 -msse2 -mfpmath=sse -ftree-
>>>>>>>>> vectorize
>>>>>>>>> -ftree-vectorizer-verbose=2 -DUNIX -DMACOSX -I . -
>>>>>>>>> I ../../../pd/
>>>>>>>>> src -I
>>>>>>>>> ../shared -c -o widgettype.o widgettype.c
>>>>>>>>> In file included from widgettype.c:16:
>>>>>>>>> setup.wiq:2: error: ‘e’ undeclared here (not in a function)
>>>>>>>>> setup.wiq:2: error: syntax error before ‘package’
>>>>>>>>> In file included from widgettype.c:16:
>>>>>>>>> setup.wiq:2:29: error: too many decimal points in number
>>>>>>>>> setup.wiq:4:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:5:3: error: invalid preprocessing directive #glue
>>>>>>>>> setup.wiq:6:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:7:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:8:3: error: invalid preprocessing directive #way
>>>>>>>>> setup.wiq:9:3: error: invalid preprocessing directive #right
>>>>>>>>> setup.wiq:11:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:14:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:18: error: syntax error before ‘{’ token
>>>>>>>>> setup.wiq:23:3: error: invalid preprocessing directive #valid
>>>>>>>>> setup.wiq:32:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:33:3: error: invalid preprocessing directive #In
>>>>>>>>> setup.wiq:34:3: error: invalid preprocessing directive #try
>>>>>>>>> setup.wiq:39:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:40:7: error: invalid preprocessing directive #pd
>>>>>>>>> setup.wiq:73:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:80: error: syntax error before ‘{’ token
>>>>>>>>> setup.wiq:99: error: syntax error before ‘{’ token
>>>>>>>>> setup.wiq:106:3: error: invalid preprocessing directive #LATER
>>>>>>>>> setup.wiq:111: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:131:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:133:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:148:3: error: invalid preprocessing directive #puts
>>>>>>>>> setup.wiq:150:7: error: invalid preprocessing directive #puts
>>>>>>>>> setup.wiq:154: error: ‘catch’ undeclared here (not in a
>>>>>>>>> function)
>>>>>>>>> setup.wiq:154: error: syntax error before ‘{’ token
>>>>>>>>> setup.wiq:175:3: error: invalid preprocessing directive #puts
>>>>>>>>> setup.wiq:187: error: syntax error before ‘&’ token
>>>>>>>>> setup.wiq:187: error: ‘concat’ undeclared here (not in a
>>>>>>>>> function)
>>>>>>>>> setup.wiq:187: error: syntax error before ‘tcl’
>>>>>>>>> setup.wiq:188: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:192:3: error: invalid preprocessing directive
>>>>>>>>> #empirically
>>>>>>>>> setup.wiq:193:3: error: invalid preprocessing directive
>>>>>>>>> #better
>>>>>>>>> setup.wiq:196: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:202: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:207:3: error: invalid preprocessing directive
>>>>>>>>> #pdtk_canvas_mouseup
>>>>>>>>> setup.wiq:214: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:243:3: error: invalid preprocessing directive #undo
>>>>>>>>> setup.wiq:248:3: error: invalid preprocessing directive #to
>>>>>>>>> setup.wiq:273:3: error: invalid preprocessing directive
>>>>>>>>> #standard
>>>>>>>>> setup.wiq:275:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:278: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:290: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:292: error: stray ‘\’ in program
>>>>>>>>> setup.wiq:298:3: error: invalid preprocessing directive #puts
>>>>>>>>> setup.wiq:299: error: syntax error before ‘{’ token
>>>>>>>>> setup.wiq:315:3: error: invalid preprocessing directive #FIXME
>>>>>>>>> setup.wiq:318:2: error: invalid preprocessing directive #>
>>>>>>>>> setup.wiq:319:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:320:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:321:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:323:2: error: invalid preprocessing directive #>
>>>>>>>>> setup.wiq:324:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:325:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:326:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:327:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:329:2: error: invalid preprocessing directive #>
>>>>>>>>> setup.wiq:330:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:331:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:333:2: error: invalid preprocessing directive #@
>>>>>>>>> setup.wiq:336:2: error: invalid preprocessing directive #>
>>>>>>>>> setup.wiq:337:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:338:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:339:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:340:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:341:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:342:2: error: invalid preprocessing directive #.
>>>>>>>>> setup.wiq:344:2: error: invalid preprocessing directive #@
>>>>>>>>> setup.wiq:345: error: stray ‘#’ in program
>>>>>>>>> setup.wiq:345: error: stray ‘#’ in program
>>>>>>>>> make[3]: *** [widgettype.o] Error 1
>>>>>>>>> make[2]: *** [toxy_install] Error 2
>>>>>>>>> make[1]: *** [externals_install] Error 2
>>>>>>>>> make: *** [extended_install] Error 2
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> PD-dev mailing list
>>>>>>>>> [email protected]
>>>>>>>>> http://lists.puredata.info/listinfo/pd-dev
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------
>>>>>>>> ---- ---------
>>>>>>>>
>>>>>>>>
>>>>>>>> Access to computers should be unlimited and total. - the
>>>>>>>> hacker
>>>>>>>> ethic
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> PD-dev mailing list
>>>>>>> [email protected]
>>>>>>> http://lists.puredata.info/listinfo/pd-dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> PD-dev mailing list
>>>>>> [email protected]
>>>>>> http://lists.puredata.info/listinfo/pd-dev
>>>>>
>>>>> _______________________________________________
>>>>> PD-dev mailing list
>>>>> [email protected]
>>>>> http://lists.puredata.info/listinfo/pd-dev
>>>> -------------------------------------------------------------------
>>>> ----- ----
>>>> I spent 33 years and four months in active military service and
>>>> during that period I spent most of my time as a high class
>>>> muscle man for Big Business, for Wall Street and the
>>>> bankers. - General Smedley Butler
>>>> _______________________________________________
>>>> PD-dev mailing list
>>>> [email protected]
>>>> http://lists.puredata.info/listinfo/pd-dev
>> ---------------------------------------------------------------------
>> ------- ¡El pueblo unido jamás será vencido!
------------------------------------------------------------------------
----
There is no way to peace, peace is the way. -A.J. Muste
_______________________________________________
PD-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/pd-dev
