[
http://jira.codehaus.org/browse/MRM-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262913#action_262913
]
Andrew Stine commented on MRM-1467:
-----------------------------------
On linux the problem is that 'uname -p' is returning values that the 'archiva'
script isn't anticipating. It might be a system specific thing I'm not sure,
but I worked around it by having it fallthrough to 'uname -m' when 'uname -p'
returns an unexpected value.
> Archiva does not start up on Solaris 64-bit.
> --------------------------------------------
>
> Key: MRM-1467
> URL: http://jira.codehaus.org/browse/MRM-1467
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3.4
> Environment: SunOS unknown 5.10 Generic_138889-02 i86pc i386 i86pc
> Reporter: Andrew Stine
> Priority: Blocker
> Fix For: 1.3.5
>
>
> Attempting to launch causes causes error:
> $ ./apache-archiva-1.3.4/bin/archiva console
> Bad string
> Bad string
> Bad string
> Bad string
> Unable to locate any of the following binaries:
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper---32
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper---64
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper
> necessary files appear to be missing or misnamed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
