openjdk team mailing list archive

[Nobuhiro Iwamatsu <iwamatsu@xxxxxxxxxxx>]

Hi,

2010/4/22 Matthias Klose <doko@xxxxxxxxxx>:
> On 22.04.2010 01:30, Nobuhiro Iwamatsu wrote:
>>
>> Hi,
>>
>> 2010/4/17 Matthias Klose<doko@xxxxxxxxxx>:
>>>
>>> tag 575346 + moreinfo
>>> thanks
>>>
>>>> openjdk-6 6b18-1.8-1 does not yet solve this problem.
>>>>
>>>>
>>>> http://buildd.debian-ports.org/fetch.php?pkg=openjdk-6&arch=sh4&ver=6b18-1.8-1&stamp=1271323748&file=log&as=raw
>>>> A patch seems not to be applied.
>>>
>>> you could see this maybe by looking at the build log?
>>
>> I attached a patch[0] with the report of this bug. However, this patch
>> is not applied, and the same problem is left[0][1].
>>
>>>
>>>> Could you check package?
>>>
>>> sorry, enotime. it's your port.
>>>
>>
>> I see. I attached debdiff.
>> When we applied this patch, this problem is settled.
>> Could you apply?
>
> the patch doesn't make sense. you are patching an auto-generated file, the
> source file is acinclude.m4. Now unpacking the openjdk-6_6b18-1.8-1.dsc I
> see that both acinclude.m4 and configure do have this patch applied. Or does
> running autogen.sh fix the configure file for you?
>
I didn't know acinclude.m4. Thank you.

> please use the patch system only for patches made inside the openjdk
> directory, which gets unpacked during the build.
>

How should I have it when I apply a patch besides the source which I
did unpack of?
I made a patch with quilt and attached.

Of course I report this revision to an up stream, and I have the
method to wait for the next release.

Best regards,
  Nobuhiro


-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Attachment: openjdk-6_sh4_ftbfs_v2.diff
Description: application/octetstream