On 2008-07-18, noi ance <noi@siam.com> wrote:
> On Thu, 17 Jul 2008 09:55:30 +0000, Jan Wielemaker typed this message:
>> gollem:/home/jan # zypper install -D -t pattern devel_java-32bit
>> Reading installed packages...
>>
>> The following NEW pattern is going to be installed:
>> devel_java-32bit
>>
>>
>> No additional space will be used or freed after the operation.
>> Continue? [YES/no]:
>>
>> That is getting weird. I guess it should use space!? No matter what I
>> enter on the prompt (return, y, Y, YES), it immediately returns. Same
>> without -D.
>>
>> What do I miss? I also tried hard to find this pattern in the YaST
>> software management, but I can't find it.
>>
>> Puzzled --- Jan
>
> Really not sure what you tried to do. -D is the option to specify a
> repository, and I don't know what is -t pattern.

According to "man zypper", after zypper install, -D means dry-run and -t
pattern must be used to install packages belonging to a pattern. man
zypper and zypper --help give output that is a bit confusing ...

> Basics are you can still download whatever .rpm you think you need and
> install it using rpm -Uvh java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm or whatever.

I know, but as the AMD64 version is already installed, I loose that one.
I want both ...

> And I note the OpenSuse wiki on installing Java
>
> http://en.opensuse.org/Installing_Sun's_Java_on_SUSE_Linux#Switching_betw een_two_different_Java_JREs_or_SDKs

Thanks (though the repository link is broken :-()

--- Jan

Jan Wielemaker wrote:

> I need to build a 32-bit binary of a package that links against JVM on
> what is otherwise a 64-bit install of SuSE 11.0. For all other
> required libraries there are 32-bit development versions, but not for
> Java.
>
> Is there a way to install suse/i586/java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm
> alongsite suse/x86_64/java-1_6_0-sun-1.6.0.u6-8.1.x86_64.rpm?
>
> I guess I can unpack the RPM and install the files, for example
> through rpm2cpio. Would that work, and more importantly would it
> work without getting into trouble with automatic updates, etc.?
>
> Thanks --- Jan

I played with this issue some time ago on my suse 11 dev machine, had the same need for using native java 32 bit libs on 64 bit machine. Tough you could use rpm and customize /etc/alternatives to install both architectures of one jdk via suse repos, it really just messes things up.

recommend:
- choose only one jdk from suse (for example: openjdk-1.6)
- install or compile alternative jdks for development in your home or usr/local directory. the system (suse) doesnt really have to now about / use these. For example sun binary packages (http://download.java.net/jdk6/binaries/) basically just unpack without trying to get all hooked in the system like some rpms do...

my previous setting:
- use jdk-1.5 32bit along jdk-1.6 64bit, both from suse repo / yast (in the versions list you can choose what architecture). This wasn't really optimal, and changing versions through package management often broke symlinks in /etc/alternatives, but worked for a while.

On Fri, 18 Jul 2008 09:09:25 +0000, Jan Wielemaker typed this message:

> On 2008-07-18, noi ance <noi@siam.com> wrote:
>> On Thu, 17 Jul 2008 09:55:30 +0000, Jan Wielemaker typed this message:
>>> gollem:/home/jan # zypper install -D -t pattern devel_java-32bit
>>> Reading installed packages...
>>>
>>> The following NEW pattern is going to be installed:
>>> devel_java-32bit
>>>
>>>
>>> No additional space will be used or freed after the operation.
>>> Continue? [YES/no]:
>>>
>>> That is getting weird. I guess it should use space!? No matter what
>>> I enter on the prompt (return, y, Y, YES), it immediately returns.
>>> Same without -D.
>>>
>>> What do I miss? I also tried hard to find this pattern in the YaST
>>> software management, but I can't find it.
>>>
>>> Puzzled --- Jan
>>
>> Really not sure what you tried to do. -D is the option to specify a
>> repository, and I don't know what is -t pattern.
>
> According to "man zypper", after zypper install, -D means dry-run and -t
> pattern must be used to install packages belonging to a pattern. man
> zypper and zypper --help give output that is a bit confusing ...
>
>> Basics are you can still download whatever .rpm you think you need and
>> install it using rpm -Uvh java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm or
>> whatever.
>
> I know, but as the AMD64 version is already installed, I loose that one.
> I want both ...
>
>> And I note the OpenSuse wiki on installing Java
>>
>> http://en.opensuse.org/
Installing_Sun's_Java_on_SUSE_Linux#Switching_betw een_two_different_Java_JREs_or_SDKs
>
> Thanks (though the repository link is broken :-()
>
> --- Jan

Ok, must have been tired.

-D is dry-run meaning that nothing would be installed or no actions
actually executed.

-t is type as in patches (default) or pattern meaning a group of
packages like Development

When you run with the (-D) --dry-run option it displays the "no space"
line to indicate no action was taken. Without the -D it would install
the required packages.

Also, the zypper search -s -t pattern
will show all pattern packages and those with a "i" in column 1 indicates
the patterns that are installed.

I stick with the basic repos, but you could use a mirror repository if
necessary.

On 2008-07-18, titof <titof.h@gmail.com> wrote:
> Jan Wielemaker wrote:
>
>> I need to build a 32-bit binary of a package that links against JVM on
>> what is otherwise a 64-bit install of SuSE 11.0. For all other
>> required libraries there are 32-bit development versions, but not for
>> Java.
>>
>> Is there a way to install suse/i586/java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm
>> alongsite suse/x86_64/java-1_6_0-sun-1.6.0.u6-8.1.x86_64.rpm?
>>
>> I guess I can unpack the RPM and install the files, for example
>> through rpm2cpio. Would that work, and more importantly would it
>> work without getting into trouble with automatic updates, etc.?
>>
>> Thanks --- Jan
>

> I played with this issue some time ago on my suse 11 dev machine,
> had the same need for using native java 32 bit libs on 64 bit
> machine. Tough you could use rpm and customize /etc/alternatives to
> install both architectures of one jdk via suse repos, it really just
> messes things up.

> recommend:
> - choose only one jdk from suse (for example: openjdk-1.6)
> - install or compile alternative jdks for development in your home
> or usr/local directory. the system (suse) doesnt really have to
> now about / use these. For example sun binary packages
> (http://download.java.net/jdk6/binaries/) basically just unpack
> without trying to get all hooked in the system like some rpms
> do...
>
> my previous setting:
> - use jdk-1.5 32bit along jdk-1.6 64bit, both from suse repo / yast
>(in the versions list you can choose what architecture). This wasn't
>really optimal, and changing versions through package management
>often broke symlinks in /etc/alternatives, but worked for a while.

Thanks. Finally decided to unpack
java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm and
java-1_6_0-sun-devel-1.6.0.u6-8.1.i586.rpm using rpm2cpio and unpack
these in /usr/local. This appears to work just fine. It won't keep
me up to date with updates, but as this is only used to compile and
link against the jni interface that is not a big issue.

Thanks for all the comments.

--- Jan

Jan Wielemaker wrote:
> Thanks. Finally decided to unpack
> java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm and
> java-1_6_0-sun-devel-1.6.0.u6-8.1.i586.rpm using rpm2cpio and unpack
> these in /usr/local. This appears to work just fine. It won't keep
> me up to date with updates, but as this is only used to compile and
> link against the jni interface that is not a big issue.

FYI, I use 'mc' to go into RPM packages.

And normaly a rpm --force should have worked as well.

houghi
--
Let's not be too tough on our own ignorance. It's the thing that makes
America great. If America weren't incomparably ignorant, how could we
have tolerated the last eight years? -- Frank Zappa, in 1988

On 2008-07-22, houghi <houghi@houghi.org.invalid> wrote:
> Jan Wielemaker wrote:
>> Thanks. Finally decided to unpack
>> java-1_6_0-sun-1.6.0.u6-8.1.i586.rpm and
>> java-1_6_0-sun-devel-1.6.0.u6-8.1.i586.rpm using rpm2cpio and unpack
>> these in /usr/local. This appears to work just fine. It won't keep
>> me up to date with updates, but as this is only used to compile and
>> link against the jni interface that is not a big issue.
>
> FYI, I use 'mc' to go into RPM packages.

Thanks. I always hate when I get into mc after mistyping mv ...

> And normaly a rpm --force should have worked as well.

I fear that would upset package updates as I already have the 64-bit
version installed, won't it? Like this, software update will nicely
keep the 64-bit version up-to-date and not mess up the alternatives
links.

--- Jan

Nikos Chantziaras <realnc@arcor.de> wrote:
> AFAIK, Java is always 32-bit even on openSUSE x86-64. Sun never ported
> it to 64-bit.

Yes, they did. Just the plugin for the webbrowser isn't there yet:
jdk-6u6-linux-i586.bin
jdk-6u6-linux-x64.bin
both downloaded directly from Sun.
There are Java (jdk or jre) SE 6 upd. 7 packages already there too.
--
************************************************** *****************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M.Hartman@tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** *****************