Shoulde be fixed now. I hope.
andy
-----Original Message-----
From: xemacs-beta-admin(a)xemacs.org
[mailto:xemacs-beta-admin@xemacs.org]On Behalf Of Vin Shelton
Sent: Monday, November 18, 2002 4:55 PM
To: Andy(a)xemacs.org
Cc: Mats Lidell; xemacs-beta(a)xemacs.org
Subject: Re: Smoketest fails on jde.
Andy,
Any chance you could fix jde? It's not building since your update.
First there is the problem Mats identified below. I worked around
that one by touching
xemacs-packages/jde/java/src/jde/debugger/expr/Makefile.
Next I get this error on make bindist:
cp -af
/opt/build/xemacs-packages-2002-11-18-1600/xemacs-packages/jde/jav
a/src/jde/debugger/command/AttachShmem.java /opt/build/xemacs-packages->
2002-11-18-1600/xemacs-packages/jde/java/src/jde/debugger/command/
AttachSocket.java ... /opt/build/xemacs-packages-2002-11-18-1600/xemacs->
packages/jde/java/src/jde/debugger/command/Watch.java
/opt/build/xemacs-packages-2002-11-18-1600/xemacs-packages/jde/jav
a/src/jde/debugger/command/Makefile >
/home/acs/tmp/staging/etc/jde/java/src/jde/debugger/command
cp: cannot stat
`/opt/build/xemacs-packages-2002-11-18-1600/xemacs-packages/jde/ja
va/src/jde/debugger/command/Makefile': No such file or directory
make[2]: *** [binkit-common] Error 1
make[2]: Leaving directory
`/opt/build/xemacs-packages-2002-11-18-1600/xemacs-packages/jde'
make[1]: *** [jde/bindist.target] Error 2
make[1]: Leaving directory
`/opt/build/xemacs-packages-2002-11-18-1600/xemacs-packages'
make: *** [xemacs-packages/bindist.target] Error 2
Can you please investigate and fix?
Thanks,
Vin
Mats Lidell <matsl(a)contactor.se> writes:
>>>>>> rendhalver wrote:
>
> rendhalver> cool thanks dude
>
> Now with 21.4.10 the build progresses longer. This time there is an
> error during the "install". (I do "make all install" to check
for bugs
> during the install step too. Some packages does a bit during install
> so I have found it useful.)
>
> cp --force --recursive --symbolic-link
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/ASCII_UCodeESC_CharStream.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/ExpressionParserConstants.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/ExpressionParser.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/ExpressionParserTokenManager.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/LValue.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/ParseException.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/Token.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/TokenMgrError.java >
/home/matsl/work/smoketest/build/packages/xemacs-packages
/jd!
> e/java/src/jde/debugger/expr/Expr.jj
/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/java
/src/jde/debugger/expr/Makefile >
/home/matsl/work/smoketest/build/packages/../xemacs-packages/etc/j
de/java/src/jde/debugger/expr
> cp: cannot stat
`/home/matsl/work/smoketest/build/packages/xemacs-packages/jde/jav
a/src/jde/debugger/expr/Makefile': No such file or directory
> make[2]: *** [binkit-common] Error 1
> make[2]: Leaving directory
`/home/matsl/work/smoketest/build/packages/xemacs-packages/jde'
> make[1]: *** [jde/install.target] Error 2
> make[1]: Leaving directory
`/home/matsl/work/smoketest/build/packages/xemacs-packages'
> make: *** [xemacs-packages/XEMACS.install] Error 2
> ------ End of build -- all from top level
>
> rendhalver> that would be cool if you have the spare processor cycles
> rendhalver> though building mule packages without a mule enabled
> rendhalver> XEmacs is probably pointless
>
> I'll look into it. For now I check in CVS each hour for new stuff and
> if there is I do a complete rebuild.
>
> You'll find the builds here:
> "http://labb.contactor.se/~matsl/smoketest/logs/"
>
> There is no fancy Web page yet so you'll have to look in the latest
> log to find out whether the build succeeded or not. The size of the
> log gives a hint though.
>
> Yours
> --
> %% Mats