maven...

[Oliver Falk]

On 09/17/2007 03:59 PM, Deepak Bhole wrote:
> * Oliver Falk <oliver at linux-kernel.at> [2007-09-17 08:43]:
>> On 09/05/2007 10:02 PM, Deepak Bhole wrote:
>>> On Sat, 2007-09-01 at 00:09 +0100, David Woodhouse wrote:
>>>> On Fri, 2007-08-31 at 16:27 -0400, Deepak Bhole wrote:
>>>>> By biggest worry is ppc. Last time it was tried, there were failures
>>>>> specific to ppc. While it can be exclude arch'd, I would really like to
>>>>> avoid doing that.
>>>>>
>>>>> Here is the ppc bug for the record:
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=239123
>>>> I went rushing to check on that... and then realised you meant ppc64,
>>>> not ppc. We keep the ppc ExcludeArch list fairly much empty, but ppc64
>>>> userspace is less of a priority (since we actually run everything 32-bit
>>>> even on ppc64 hardware, unless there's some real _benefit_ to using
>>>> 64-bit userspace).
>>>>
>>> Ah sorry, I should have clarified that; Yes, it is ppc64 that is an
>>> issue. ppc itself is fine. I did a scratch build earlier and it went
>>> through fine:
>>>
>>> http://koji.fedoraproject.org/koji/taskinfo?taskID=144642
>>>
>>> I will build maven in F8 with ExcludeArch for ppc64 for the time being.
>>>
>>>
>>>> I had a brief look, but even with bootstrap mode enabled it seems to
>>>> require maven-* packages which aren't available.
>>>>
>>> I have built the base dependencies and maven2 should be buildable in
>>> bootstrap mode now (set _with_bootstrap to 1 in the spec file). Building
>>> in ppc64 for F8 still gives an error btw:
>>>
>>> http://koji.fedoraproject.org/koji/getfile?taskID=144590&name=build.log
>>>
>>>> If you need an account on a suitable machine to poke at this, let me
>>>> have a SSH public key.
>>>>
>>> I am busy with some other stuff for the next little while, but I may
>>> take you up on the offer when I can get around to it :) In the mean
>>> time, since maven2 is buildable on ppc, it will be available as ppc arch
>>> on ppc64 in F8 -- there is no compelling reason that I can think of that
>>> necessitates a ppc64 version at this time.
>> What exactly is the problem with maven on ppc64? Maybe I have the same
>> problem with maven on alpha :-)
>>
>> -of
>>
> 
> The java process exits with error code 255 despite successfully building
> maven2, on ppc64. This behaviour is unique to ppc64, and does not occur on
> other archs. You can see the build log for such a build here:
> 
> http://koji.fedoraproject.org/koji/getfile?taskID=144590&name=build.log
> 
> I can reliably reproduce this on other ppc64 boxes when I try to build
> maven2. However, narrowing it down to a smaller testcase is proving more 
> cumbersome than I expected :/

OK. Not similar to mine - which is also 'funny':
Building project in
/home/oliver/cvs/devel/maven2/maven2/maven2/maven-profile
------------------------------------------------------------------
Cleaning /home/oliver/cvs/devel/maven2/maven2/maven2/maven-profile/target...
Model exists!
Checking for dependencies ...
Generating model bindings for version '1.0.0' from
'/home/oliver/cvs/devel/maven2/maven2/maven2/maven-profile/profiles.mdo'
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
./bootstrap.sh: line 47: 11961 Illegal instruction     $JAVACMD
$MAVEN_OPTS -jar
bootstrap/bootstrap-installer/target/bootstrap-installer.jar
--prefix=$PREFIX $ARGS
+ ret=132
+ '[' 132 '!=' 0 ']'
+ exit 132


-of