Bug 144259 - media-libs/panda3d-1.2.3 version bump
|
Bug#:
144259
|
Product: Gentoo Linux
|
Version: 2006.0
|
Platform: All
|
|
OS/Version: Other
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: maintainer-needed@gentoo.org
|
Reported By: lstep@adelux.fr
|
|
Component: Ebuilds
|
|
|
URL:
http://panda3d.org/
|
|
Summary: media-libs/panda3d-1.2.3 version bump
|
|
Keywords: EBUILD
|
|
Status Whiteboard:
|
|
Opened: 2006-08-17 16:09 0000
|
Please find attached panda3d-1.2.3.ebuild, released May 24, 2006 fixing a
serious bug in panda3d 1.2.2 (no ebuild anyway for 1.2.2).
Panda3D is a 3D engine: a library of subroutines for 3D rendering and game
development. The library is C++ with a set of Python bindings. Game development
with Panda3D usually consists of writing a Python program that controls the the
Panda3D library.
Please note that the compilation of Panda3D doesn't work with gcc version
3.4.4. It works fine with gcc 3.4.6. I'll add a dependency in a revised ebuild
version shortly.
Just to sort of make the timeline on this apparent, this might take awhile to
get in. This is mainly because every single release I have to patch
makepanda.py to use custom CFLAGS and adhere to multilib lib/lib64 logic. This
ends up being a fairly large patch.
Maybe you guys are interested in this?
*** Bug 217064 has been marked as a duplicate of this bug. ***
*** Bug 217066 has been marked as a duplicate of this bug. ***
Original bug from 2006 ...
Guess it probably won't get fixed..
The newer ebuilds I added have one issue that causes me a problem and that is
with the python bindings for direct need to be added as
ln -s /opt/panda3d/direct/ /usr/lib/python2.4/site-packages/
and for pandac
ln -s /opt/panda3d/pandac/ /usr/lib/python2.4/site-packages/
and also
edit /usr/lib/python2.4/site-packages/panda3d.pth
and add /opt/panda3d/lib
I am not 100% sure how to add this to an ebuild
(In reply to comment #10)
> Original bug from 2006 ...
> Guess it probably won't get fixed..
> The newer ebuilds I added have one issue that causes me a problem and that is
> with the python bindings for direct need to be added as
> ln -s /opt/panda3d/direct/ /usr/lib/python2.4/site-packages/
> and for pandac
> ln -s /opt/panda3d/pandac/ /usr/lib/python2.4/site-packages/
> and also
> edit /usr/lib/python2.4/site-packages/panda3d.pth
> and add /opt/panda3d/lib
>
> I am not 100% sure how to add this to an ebuild
>
I figured it out.. will add to the ebuild
as a note both the 1.4.2 and 1.5.0 build and are functional.
after using these you can go into /opt/panda3d/samples and run any of them.
tested on both x86 and x86_64
cheers
(In reply to comment #14)
> as a note both the 1.4.2 and 1.5.0 build and are functional.
> after using these you can go into /opt/panda3d/samples and run any of them.
>
x86 - I tried the 1.5.0 ebuild ...
- needed to add /opt/panda3d to the panda3d.pth otherwise it failed to import
direct.<stuff>
- all samples progs that I tried generated segfaults as they started. Ditto the
minimal
hello world from the website. Running python under gdb, this mentioned free()
in libc.so.6
(no other debug info available)
I'm on a ~x86 system.
I've used this e-build renamed to 1.5.2 and it installed just fine.
I only had to add
/opt/panda3d
to the installed file /usr/lib/python2.5/site-packages/panda3d.pth
I'll upload the modified e-build that adds this and name it 1.5.2
Samples run fine, except two or three but that does not seem to have any
relation to this ebuild.
I also noticed that changing permissions on the /opt/panda3d/modelcache/ folder
so that it is writable by the users group makes samples run faster as they are
able to use the modelcache feature when run as a regular user.
Thanks for your job Joel.
I have just installed panda3d 1.5.2 on my amd64 system.
The path set in /etc/env.d/50panda3d is not correct.
The panda3d libs are in /opt/panda3d/lib and NOT /opt/panda3d/lib64.
The corrections to the ebuild are:
54,56d53
< sed -i -e "s:lib:$(get_libdir):g" \
< ${D}/etc/env.d/50panda3d \
< || die "libdir patching failed"
Its the same problem with the 1.4.2 and 1.5.0 ebuilds.
With the correct path set, my initial test with samples work :-)
However, I have not attached a new ebuild as Joel De Gan write he has tested
1.4.2 and 1.5.0 on a x86_64 arch.
I think that is a mistake by Joel, can you check again Joel?
bumped to 1.5.2 in cvs, should be available on the mirrors in a few hours.