Re: [xmlblaster] cannot build under redhat9.0,why?

[Marcel Ruff <mr at marcelruff.info>]

?? wrote:

> rt,
> Hello! Is there anyone can give me some suggestion or hints? I cannot build xmlblaster version 0.846 under RH9.0
> and after I ran ./build.sh all, it give me the messages below:
> 			
> regards
> jiang
>
>
> [root at myhost xmlBlaster]# ./build.sh all
> Buildfile: build.xml
>
> prepare:
>     [echo] os.family=unix os.name=Linux
>     [echo] Build timestamp = 05/05/2003 02:23 ?? version = 0.846
>     [echo] xmlBlaster.home=/working/java/xmlBlaster
>
> java-corba-idl:
>     [echo] Converting idl...
>     [echo] Comparing ./src/java/org/xmlBlaster/protocol/corba/xmlBlaster.idl to ./src/java/org/xmlBlaster/protocol/corba/serverIdl/Server.java
>     [echo] CORBA stubs and skeletons are up to date
>
> prepare-src:
>
> xmlBlaster:
>     [copy] Copying 446 files to /working/java/xmlBlaster/build/src/xmlBlaster
>     [copy] Replacing:  at version at  -> 0.846
>     [copy] Replacing:  at build.timestamp at  -> 05/05/2003 02:23 ??
>     [copy] Replacing:  at build.java.vendor at  -> Sun Microsystems Inc.
>     [copy] Replacing:  at build.java.version at  -> 1.3.1_08
>     [copy] Replacing:  at version at  -> 0.846
>     [copy] Replacing:  at build.timestamp at  -> 05/05/2003 02:23 ??
>
> BUILD FAILED
> file:///working/java/xmlBlaster/build.xml:397: Failed to copy /working/java/xmlBlaster/src/java/org/xmlBlaster/protocol/http/persistentWindow/clown.gif to 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /working/java/xmlBlaster/build/src/xmlBlaster/org/xmlBlaster/protocol/http/persistentWindow/clown.gif due to null
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` 
> what cause this? I build it successful under win2k

Hi jiang,

Check if the file

xmlBlaster/src/java/org/xmlBlaster/protocol/http/persistentWindow/clown.gif

exists.

Is your hard disk full? Check it with the 'df' command.

The 'due to null' seems to come from 'ant', i don't
know what this error could be related to.
Probably you should check this on the 'ant' mailing list.
On my Linux i never had such a problem.

regards,

Marcel