Hi Damien,

I've been trying again with newer openjdk-7 7~u3-2.1.1~pre1-2, using
dpkg-buildpackage, and keeping a log this time of a single build
attempt, immediately after extracting from source.

With -j2 I am seeing this error first:

>  Error: <dialoginput.bolditalic.korean-nanumcoding> entry is missing!!!
> 
>  Error: <allfonts.korean-un> entry is missing!!!
> 
>  Error: <allfonts.korean-baekmuk> entry is missing!!!
> !!THERE ARE 42 ERROR(S) IN THE FONTCONFIG FILE, PLEASE CHECK ITS CONTENT!!
> 
> make[6]: *** 
> [/home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build/lib/fontconfig.Ubuntu.bfc]
>  Error 1
> make[6]: Leaving directory 
> `/home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk/jdk/make/sun/awt'

I then see another error where patches/boot/javafiles.patch is applied
twice, but that may be a consequence of the above error.


With -j4 there seem to be races, including:

> abs_bin_zip=`cd 
> /home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/dist/lib
>  ; pwd`/bin.zip ; \
>         ( cd 
> /home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba ; find 
> lib -name "*.idl" -print | zip -q $abs_bin_zip -@ ) ;
> /home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/classes:
>  No such file or directory
> Error adding . (in directory 
> /home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/classes)
>  to jar archive!
> make[4]: *** 
> [/home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/dist/lib/classes.jar]
>  Error 1
> make[4]: *** Waiting for unfinished jobs....
> find: `lib': No such file or directory
> 
> zip error: Nothing to do! 
> (/home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/dist/lib/bin.zip)
> make[4]: *** 
> [/home/steven/openjdk-7-7~u3-2.1.1~pre1/build/openjdk.build-boot/corba/dist/lib/bin.zip]
>  Error 12

Then the build stops before I get to the fontconfig issue.

Something was trying to package up CORBA libraries before they have been
built.  And there are many unsafe uses of ';' instead of '&&' here which
could lead to other problems.


We should probably try to fix these issues with parallelism because it
makes comparing build logs very difficult.  I suspect that when I
specify -j1 it is still being overridden somewhere.  And the issues seen
on buildds may simply be some race during build (e.g. some output file
used before it's fully built).

Regards,
-- 
Steven Chamberlain
[email protected]


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to