> On Feb 3, 2016, at 1:08 PM, Scott Palmer <swpal...@gmail.com> wrote:
> 
> 
>> On Feb 3, 2016, at 11:40 AM, Chris Bensen <chris.ben...@oracle.com> wrote:
>> 
>> On Feb 2, 2016, at 7:27 PM, Scott Palmer <swpal...@gmail.com> wrote:
>>> 
>>> Note that this is a RPM-based system, apt-get is not available, yum is.
>>> 
>>> yum install libX11
>> 
>> What is the Linux system you are running?
> 
> It is a version of CentOS.  (Created within my company with minor tweaks for 
> branding purposes.)

When submitting a bug, make sure the test case works on Oracle Linux or Ubuntu 
since those are the only “supported” version of Linux.

> 
> 
>>> 
>>> It seems to be that javapackager has made a mistake and is claiming to 
>>> depend on the 32-bit packages even though it really requires the 64-bit 
>>> packages.
>> 
>> That’s what it’s sounding like to me. Looking at the code for the RPM 
>> bundler there isn’t anything I can find offhand that would suggest this. 
>> Bundling with 32/64-bit is triggered off the JDK used. Note that you have to 
>> bundle the same bitness JRE as the JDK. It should fail if it isn’t but that 
>> isn’t the case yet and that isn’t your problem. It appears the RPM generated 
>> is 32-bit. Unless you are bundling a 32-bit JRE and the RPM bundler keys off 
>> the native libraries used. Can you check the launcher executable? I think 
>> it’d be:
>> 
>> $ file myserver-1.0-1.x86_64/app/myserver
> 
> I had to extract the launcher from the .rpm.  There is no version of it that 
> is sitting around in the output folder.
> 
> myserver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
> linked (uses shared libs), for GNU/Linux 2.6.15, 
> BuildID[sha1]=0x7e6522a86eca91b45cfb4dfa5defbddac0b1294a, not stripped
> 
> 
> So the 64-bit launcher is bundled.
> 
> 
>> 
>> Can you file a minimum test case along with the Linux system used so we can 
>> prioritize with other bugs and find a solution?
> 
> I’ll try to put something together.  I’m still eager to find a workaround 
> that I can implement with 8u72.
> 
> 
> Scott
> 
> 
>> 
>> Chris
>> 
>> 
>>> Scott 
>>> 
>>> 
>>>> On Feb 2, 2016, at 7:03 PM, Chris Bensen <chris.ben...@oracle.com> wrote:
>>>> 
>>>> This list or the Deployment blog 
>>>> (https://blogs.oracle.com/talkingjavadeployment/) are the best places to 
>>>> get help with the javapackager.
>>>> 
>>>> Is your app built with the 64-bit or 32-bit packager? I noticed “x86_64” 
>>>> appended to the name. If it’s 32-bit you could try running:
>>>> 
>>>> sudo apt-get install libx11-6:i386
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>>> On Feb 2, 2016, at 1:49 PM, Scott Palmer <swpal...@gmail.com> wrote:
>>>>> 
>>>>> What's the best place to go to get help with using the javapackager ?
>>>>> 
>>>>> I've read the docs, but things aren't working smoothly and it would be
>>>>> helpful if there were some known working examples to base things on.  I'm
>>>>> not finding any examples that use the -daemon or -BserviceHint=true
>>>>> options, for example.
>>>>> 
>>>>> I attempted to make a .rpm that installs a service/daemon but when I try 
>>>>> to
>>>>> install it, it fails claiming the following dependencies cannot be met:
>>>>> 
>>>>>    libX11.so.6 is needed by myserver-1.0-1.x86_64
>>>>>    libXext.so.6 is needed by myserver-1.0-1.x86_64
>>>>>    libXi.so.6 is needed by myserver-1.0-1.x86_64
>>>>>    libXrender.so.1 is needed by myserver-1.0-1.x86_64
>>>>>    libXtst.so.6 is needed by myserver-1.0-1.x86_64
>>>>>    libasound.so.2 is needed by myserver-1.0-1.x86_64
>>>>> 
>>>>> Considering the app already runs fine on this same system, I'm a bit
>>>>> confused that it is complaining of missing dependencies.
>>>>> 
>>>>> Scott
> 

Reply via email to