Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 87774 - app-pda/pilot-link-0.11.8-r1 fails on amd64
Summary: app-pda/pilot-link-0.11.8-r1 fails on amd64
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 All
: High normal (vote)
Assignee: Gentoo PDA project
URL:
Whiteboard:
Keywords:
: 91668 92834 97094 111434 (view as bug list)
Depends on:
Blocks: 66087
  Show dependency tree
 
Reported: 2005-04-03 06:08 UTC by Sebastian Spaeth
Modified: 2005-11-04 00:44 UTC (History)
10 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
experimental ebuild to make it compile on amd64 (might_just_work.tgz,1.49 KB, application/octet-stream)
2005-06-30 06:13 UTC, Philipp Weinfurter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Spaeth 2005-04-03 06:08:13 UTC
During emerge this error comes up and compilation fails:

make[3]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8-r1/work/pilot-link-0.11.8/bindings/Java'
cp libjpisock.so /opt/sun-jdk-1.5.0.01/jre/lib/i386/
ACCESS DENIED  open_wr:   /opt/sun-jdk-1.5.0.01/jre/lib/i386/libjpisock.so
cp: regular file ,,/opt/sun-jdk-1.5.0.01/jre/lib/i386/libjpisock.so" cannot be created: no access rights

Of course this doesn't work. I don't have /opt/sun-jdk-1.5.0.01/jre/lib/i386/
but I have /opt/sun-jdk-1.5.0.01/jre/lib/amd64/
so somewhere the wrong (hardcoded?) path is specified.
Comment 1 Martin Allchin 2005-04-03 15:54:20 UTC
You could create a symlink to side-step the issue for now. Silly bug that needs fixing upstream I guess.
Comment 2 Sebastian Spaeth 2005-04-04 02:52:04 UTC
OK, will create a symlink. I send a mail to the pilot-link devl list. Hopefully they fix it. Should this be left open until then, or should it be closed?
Comment 3 gentoo@danielquinn.org 2005-04-04 09:44:54 UTC
well i've got the same issue and have created a symlink from i386 to amd64 with no change in behaviour.  did i miss something?
Comment 4 Thomas Matthijs (RETIRED) gentoo-dev 2005-04-04 10:06:08 UTC
its also a bad idea to install it directly into JAVA_HOME, since that dir gets changed when there is an update to the jdk/jre
Comment 5 Greg Tassone 2005-04-22 11:48:14 UTC
This is still an open issue, apparently.  I did some tests again today and it's still looking for the i386 directory.

Any thoughts for a fix?  I haven't had time to build a patch for this myself.
Comment 6 Jeff Norman 2005-05-04 19:12:29 UTC
Creating symlink seems to work for me.  Ugly though.  Wish I could find where upstream this was hard coded as i386.
Comment 7 Greg Tassone 2005-05-05 13:54:18 UTC
FYI:  Creating a symlink does NOT work for me.  I still get sandbox violations:

------------
cp libjpisock.so /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/
ACCESS DENIED  open_wr:   /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libjpisock.so
cp: cannot create regular file `/opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libjpisock.so': Permission denied
------------
Comment 8 Alastair Tse (RETIRED) gentoo-dev 2005-05-08 13:41:57 UTC
*** Bug 89823 has been marked as a duplicate of this bug. ***
Comment 9 Alastair Tse (RETIRED) gentoo-dev 2005-05-08 13:42:34 UTC
*** Bug 91668 has been marked as a duplicate of this bug. ***
Comment 10 Alastair Tse (RETIRED) gentoo-dev 2005-05-17 04:54:07 UTC
*** Bug 92834 has been marked as a duplicate of this bug. ***
Comment 11 Simon Stelling (RETIRED) gentoo-dev 2005-06-26 02:29:29 UTC
*** Bug 97094 has been marked as a duplicate of this bug. ***
Comment 12 Philipp Weinfurter 2005-06-30 05:26:28 UTC
There seem to be a couple of problems here...
1) the two amd64-patches patch Makefile.am But automake is never run by the
installation scripts, right? So they should patch Makefile.in to have any effect.

2) java_install_amd64.patch tries to copy to ${JAVABASE}/jre/lib/amd64/ which is
not relative to $(DESTDIR), hence the sandbox-violation, i think. Why not simply
install it in $(DESTDIR)$(libdir)/ ?

3) I don't see how the fPIC patch should take effect. It patches Makefile.in but
is applied *after* econf has been called. 

Comment 13 Philipp Weinfurter 2005-06-30 06:13:38 UTC
Created attachment 62318 [details]
experimental ebuild to make it compile on amd64

beware, this is just a quick hack to get in to compile on my system (amd64)
- get rid of compile_amd64 patch
- new ebuild moves fPIC patch to the beginning of src_unpack()
- fPIC patch also adds $(CXXFLAGS)
- install_amd64 patch installs into $(DESTDIR)$(libdir)/
Comment 14 Greg Tassone 2005-07-06 21:23:18 UTC
Good show!  I've been very busy lately or I would have tested this sooner.

I used your attached ebuild and patches and created a small Portage overlay for
this.  It worked like a charm.  Thanks very much for taking the time to dig into
the build files and figure out what was wrong (I hadn't had the time).

** To the Gentoo Devs:  I recommend incorporating these changes into the Portage
tree ASAP (after sufficient quality review, of course -- but the changes seem
minor enough).

Also, for anyone else that wants a copy of my Portage overlay to fix this just
let me know.
Comment 15 Alastair Tse (RETIRED) gentoo-dev 2005-07-07 02:57:22 UTC
i still don't know whether adding -fPIC to CXXFLAGS is the right way to go? can amd64 folks confirm this?
Comment 16 Philipp Weinfurter 2005-07-07 04:54:34 UTC
(In reply to comment #15)
> i still don't know whether adding -fPIC to CXXFLAGS is the right way to go?
can amd64 folks confirm this?

But that's not what the patch does. -fPIC is only added to the compile options
for libjpisock.c, which should be ok.

Comment 17 Simon Stelling (RETIRED) gentoo-dev 2005-07-07 08:13:16 UTC
-fPIC must be applied to (and only to) shared objects, generally adding -fPIC to
C(XX)FLAGS is a very bad idea. This is policy on all arches, so please apply the
changes unconditionally.

(hint: http://dev.gentoo.org/~plasmaroo/devmanual//archs/amd64/ )
Comment 18 Alastair Tse (RETIRED) gentoo-dev 2005-07-08 03:12:02 UTC
great. this should finally fix it. thanks for the patch and also the amd64 devs for pointing me to some 
docs about fPIC.  i'm committing this into -r1 rather than a revision bump since it doesn't add any new 
features, just fixes compile problems.
Comment 19 Jakub Moc (RETIRED) gentoo-dev 2005-11-04 00:44:28 UTC
*** Bug 111434 has been marked as a duplicate of this bug. ***