[arch-general] AUR: gcc-java-4.3.3.tar.bz2.part ==> ERROR: Build Failed.

[David C. Rankin]

On Friday 13 November 2009 02:48:28 and regarding:
> Evangelos Foutras wrote:
<snip>
> 
> That is due to how gcc detects language settings so is a standard line
> in our gcc packages.
> 
> Anyway, that package really needs updating...  I'd surprized if it
> worked at all in its current form.
> 

Evangelos,

	Your wisdom preceeds you! After a lllooonnnggg time building, the build 
aborted. Here is the context of where the build failed:


checking dependency style of  /home/david/arch/bs/gcc-gcj/gcc-
gcj/src/gcc-4.3.3/build/./gcc/xgcc -shared-libgcc -B/home/david/arch/bs/gcc-
gcj/gcc-gcj/src/gcc-4.3.3/build/./gcc -nostdinc++ -L/home/david/arch/bs/gcc-
gcj/gcc-gcj/src/gcc-4.3.3/build/x86_64-unknown-linux-gnu/libstdc++-v3/src -
L/home/david/arch/bs/gcc-gcj/gcc-gcj/src/gcc-4.3.3/build/x86_64-unknown-linux-
gnu/libstdc++-v3/src/.libs -B/usr/x86_64-unknown-linux-gnu/bin/ -B/usr/x86_64-
unknown-linux-gnu/lib/ -isystem /usr/x86_64-unknown-linux-gnu/include -isystem 
/usr/x86_64-unknown-linux-gnu/sys-include... gcc3
checking for x86_64-unknown-linux-gnu-as... /home/david/arch/bs/gcc-gcj/gcc-
gcj/src/gcc-4.3.3/build/./gcc/as
checking for x86_64-unknown-linux-gnu-ld... /home/david/arch/bs/gcc-gcj/gcc-
gcj/src/gcc-4.3.3/build/./gcc/collect-ld
checking for x86_64-unknown-linux-gnu-ar... ar
checking for x86_64-unknown-linux-gnu-ranlib... ranlib
checking for gawk... (cached) gawk
checking for jar... jar
checking for zip... no
checking for unzip... unzip
Illegal option: @
Usage: jar {ctxui}[vfm0Me] [jar-file] [manifest-file] [entry-point] [-C dir] 
files ...
Options:
    -c  create new archive
    -t  list table of contents for archive
    -x  extract named (or all) files from archive
    -u  update existing archive
    -v  generate verbose output on standard output
    -f  specify archive file name
    -m  include manifest information from specified manifest file
    -e  specify application entry point for stand-alone application
        bundled into an executable jar file
    -0  store only; use no ZIP compression
    -M  do not create a manifest file for the entries
    -i  generate index information for the specified jar files
    -C  change to the specified directory and include the following file
If any file is a directory then it is processed recursively.
The manifest file name, the archive file name and the entry point name are
specified in the same order as the 'm', 'f' and 'e' flags.

Example 1: to archive two class files into an archive called classes.jar:
       jar cvf classes.jar Foo.class Bar.class
Example 2: use an existing manifest file 'mymanifest' and archive all the
           files in the foo/ directory into 'classes.jar':
       jar cvfm classes.jar mymanifest -C foo/ .

configure: error: cannot find neither zip nor jar, cannot continue
make[1]: *** [configure-target-libjava] Error 1
make[1]: Leaving directory `/home/david/arch/bs/gcc-gcj/gcc-
gcj/src/gcc-4.3.3/build'
make: *** [all] Error 2
==> ERROR: Build Failed.
    Aborting...


	Getting that little pdftk build has become a real challenge. What needs to be 
done to update the package so it will build again?


-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com