Mark,

yes. but this is actually the only project in which svn appears to be  
doing this, and I would like to trust the versioning tools.
I did a fresh checkout, first from interpreter/trunk but that made no  
difference.
Then I rm -rf'ed the whole tree - same thing.

I agree that there is something wrong. It does not make anything  
before deciding it needs DBCSSupport.cpp for a library.
Can you see anything from this below dry verbose make run?

[venetia:oorexx/interpreter/trunk] rvjansen% make -n
make  all-recursive
failcom='exit 1'; \
        for f in x $MAKEFLAGS; do \
          case $f in \
            *=* | --[!k]*);; \
            *k*) failcom='fail=yes';; \
          esac; \
        done; \
        dot_seen=no; \
        target=`echo all-recursive | sed s/-recursive//`; \
        list='api kernel rexxapi utilities extensions samples'; for subdir in  
$list; do \
          echo "Making $target in $subdir"; \
          if test "$subdir" = "."; then \
            dot_seen=yes; \
            local_target="$target-am"; \
          else \
            local_target="$target"; \
          fi; \
          (cd $subdir && make  $local_target) \
          || eval $failcom; \
        done; \
        if test "$dot_seen" = "no"; then \
          make  "$target-am" || exit 1; \
        fi; test -z "$fail"
Making all in api
make[2]: Nothing to be done for `all'.
Making all in kernel
failcom='exit 1'; \
        for f in x $MAKEFLAGS; do \
          case $f in \
            *=* | --[!k]*);; \
            *k*) failcom='fail=yes';; \
          esac; \
        done; \
        dot_seen=no; \
        target=`echo all-recursive | sed s/-recursive//`; \
        list='messages'; for subdir in $list; do \
          echo "Making $target in $subdir"; \
          if test "$subdir" = "."; then \
            dot_seen=yes; \
            local_target="$target-am"; \
          else \
            local_target="$target"; \
          fi; \
          (cd $subdir && make  $local_target) \
          || eval $failcom; \
        done; \
        if test "$dot_seen" = "no"; then \
          make  "$target-am" || exit 1; \
        fi; test -z "$fail"
Making all in messages
make[3]: Nothing to be done for `all'.
make[3]: *** No rule to make target `platform/unix/DBCSSupport.cpp',  
needed by `librexx_la-DBCSSupport.lo'.  Stop.
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
[venetia:oorexx/interpreter/trunk] rvjansen% [venetia:oorexx/ 
interpreter/trunk] rvjansen% make
[venetia:oorexx/interpreter/trunk]: No match.
'make  all-recursive
Making all in api
make[2]: Nothing to be done for `all'.
Making all in kernel
Making all in messages
make[3]: Nothing to be done for `all'.
make[3]: *** No rule to make target `platform/unix/DBCSSupport.cpp',  
needed by `librexx_la-DBCSSupport.lo'.  Stop.
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
[venetia:oorexx/interpreter/trunk] rvjansen% 'make  all-recursive
Unmatched '.
[venetia:oorexx/interpreter/trunk] rvjansen% Making all in api
Making: Command not found.
[venetia:oorexx/interpreter/trunk] rvjansen% make[2]: Nothing to be  
done for `all'.
Unmatched `.
[venetia:oorexx/interpreter/trunk] rvjansen% Making all in kernel
Making: Command not found.
[venetia:oorexx/interpreter/trunk] rvjansen% Making all in messages
Making: Command not found.
[venetia:oorexx/interpreter/trunk] rvjansen% make[3]: Nothing to be  
done for `all'.
Unmatched `.
[venetia:oorexx/interpreter/trunk] rvjansen% make[3]: *** No rule to  
make target `platform/unix/DBCSSupport.cpp', needed by `librexx_la- 
DBCSSupport.lo'.  Stop.
Unmatched '.
[venetia:oorexx/interpreter/trunk] rvjansen% make[2]: *** [all- 
recursive] Error 1
make[2]:: Too many arguments.
[venetia:oorexx/interpreter/trunk] rvjansen% make[1]: *** [all- 
recursive] Error 1
make[1]:: Too many arguments.
[venetia:oorexx/interpreter/trunk] rvjansen% make: *** [all] Error 2
make:: Too many arguments.


best regards,

René.

On 11 jul 2008, at 18:52, Mark Miesfeld wrote:

> On Fri, Jul 11, 2008 at 9:41 AM, René Jansen <[EMAIL PROTECTED]>  
> wrote:
>> Are we speaking about interpreter/trunk here?  I still cannot build
>> it. I thought I'd wait a while until you guys came around to testing
>> Linux and then it would be solved, but still I see:
>
> René
>
> You've had these problems before.  <grin>  I really think you need to
> do a fresh checkout.  Just doing a svn update doesn't seem to get you
> in sync.
>
> They don't charge us for doing a fresh check out.  ;-)  I almost
> always do it on Linux when I haven't been on the system for some time.
>
> --
> Mark Miesfeld.
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to