I made a new ebuild for pivy. Reproducible: Always Maintainer wanted.
Either let us know which ebuild you want to have something for or attach the one you made.
Created attachment 209394 [details] First ebuild for Pivy
reopen as info is there
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Justin. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
(In reply to comment #4) > Hello, The Gentoo Team would like to firstly thank you for your ebuild > submission. We also apologize for not being able to accommodate you in a timely > manner. There are simply too many new packages. > > Allow me to use this opportunity to introduce you to Gentoo Sunrise. The > sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to > commit to and all users can have ebuilds reviewed by Gentoo devs for entry > into the overlay. So, the sunrise team is suggesting that you look into this > and submit your ebuild to the overlay where even *you* can commit to. =) > > Thanks, > On behalf of the Gentoo Sunrise Team, > Justin. > > [1]: http://www.gentoo.org/proj/en/sunrise/ > [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq > Hello Justin. As soon as Tommy give me permission to commit it , I will commit this in the sunrise overlay. Roelof
Checking for SWIG version... 1.3.40 Warning: Pivy has only been tested with the following SWIG versions: 1.3.25. Checking for coin-config... '/usr/bin/coin-config' Coin version... 2.4.5 Checking for Coin features... 3ds import vrml97 sound threads Checking for soqt-config... '/usr/bin/soqt-config' Checking for soqt version... 1.4.1 Checking for soxt-config... not found. Checking for sogtk-config... not found. Checking for sowin-config... not found. Preparing Inventor headers: Inventor/SbDPRotation.h Inventor/SbBox3f.h Inventor/SbVec2d.h Inventor/SbVec2s.h Inventor/SbColor4f.h Inventor/SbMatrix.h Inventor/SbName.h Inventor/SbBox2f.h Inventor/SbBox3s.h Inventor/SbVec3s.h Inventor/SbTime.h Inventor/SbVec3f.h Inventor/SoPath.h Inventor/SbViewportRegion.h Inventor/SbRotation.h Inventor/SbBox2s.h Inventor/SoType.h Inventor/SbXfBox3f.h Inventor/SoOffscreenRenderer.h Inventor/SbVec2f.h Inventor/SbString.h Inventor/SbColor.h Inventor/SbVec4f.h Inventor/SbDPMatrix.h Inventor/SbVec4d.h Inventor/SbPlane.h Inventor/SbVec3d.h Inventor/SoNodeKitPath.h Inventor/SoInput.h Inventor/SbViewVolume.h Inventor/SbDPPlane.h Inventor/SbBox2d.h Inventor/SbImage.h Inventor/engines/SoEngine.h Inventor/fields/SoMFVec3f.h Inventor/fields/SoMFBool.h Inventor/fields/SoMFEngine.h Inventor/fields/SoFieldContainer.h Inventor/fields/SoMFVec4f.h Inventor/fields/SoMFMatrix.h Inventor/fields/SoSFInt32.h Inventor/fields/SoSFPath.h Inventor/fields/SoSFUInt32.h Inventor/fields/SoSFUShort.h Inventor/fields/SoField.h Inventor/fields/SoMFRotation.h Inventor/fields/SoSFMatrix.h Inventor/fields/SoSFName.h Inventor/fields/SoSFString.h Inventor/fields/SoSFTime.h Inventor/fields/SoMFPath.h Inventor/fields/SoSFVec3f.h Inventor/fields/SoMFNode.h Inventor/fields/SoSFRotation.h Inventor/fields/SoSFPlane.h Inventor/fields/SoMFPlane.h Inventor/fields/SoMFTime.h Inventor/fields/SoSFImage.h Inventor/fields/SoMFInt32.h Inventor/fields/SoMFFloat.h Inventor/fields/SoMFString.h Inventor/fields/SoMFVec2f.h Inventor/fields/SoSFNode.h Inventor/fields/SoSFEnum.h Inventor/fields/SoSFImage3.h Inventor/fields/SoMFUShort.h Inventor/fields/SoSFVec4f.h Inventor/fields/SoMFName.h Inventor/fields/SoSFVec2f.h Inventor/fields/SoMField.h Inventor/fields/SoSFBool.h Inventor/fields/SoSFShort.h Inventor/fields/SoMFUInt32.h Inventor/fields/SoMFEnum.h Inventor/fields/SoSFTrigger.h Inventor/fields/SoSFFloat.h Inventor/fields/SoMFShort.h Inventor/fields/SoSFColor.h Inventor/fields/SoSFEngine.h Inventor/fields/SoMFColor.h Inventor/draggers/SoDragger.h Inventor/elements/SoDiffuseColorElement.h Inventor/elements/SoLazyElement.h Inventor/misc/SoBase.h Inventor/collision/SoIntersectionDetectionAction.h Inventor/lists/SbStringList.h Inventor/lists/SoFieldList.h Inventor/lists/SoEngineList.h Inventor/lists/SbPList.h Inventor/lists/SoDetailList.h Inventor/lists/SoEngineOutputList.h Inventor/lists/SoTypeList.h Inventor/lists/SoBaseList.h Inventor/lists/SoActionMethodList.h Inventor/lists/SbVec3fList.h Inventor/lists/SbIntList.h Inventor/lists/SoPickedPointList.h Inventor/lists/SoPathList.h Inventor/lists/SoNodeList.h Inventor/nodekits/SoBaseKit.h Inventor/sensors/SoDataSensor.h Inventor/sensors/SoAlarmSensor.h Inventor/sensors/SoIdleSensor.h Inventor/sensors/SoTimerSensor.h Inventor/sensors/SoOneShotSensor.h Inventor/sensors/SoTimerQueueSensor.h Inventor/sensors/SoDelayQueueSensor.h Inventor/sensors/SoPathSensor.h Inventor/sensors/SoSensor.h Inventor/sensors/SoFieldSensor.h Inventor/sensors/SoNodeSensor.h Inventor/actions/SoGLRenderAction.h Inventor/actions/SoCallbackAction.h Inventor/nodes/SoCallback.h Inventor/nodes/SoEventCallback.h Inventor/nodes/SoSelection.h Inventor/Qt/SoQtRenderArea.h Inventor/Qt/SoQt.h. === Generating pivy/gui/soqt_wrap.cpp for soqt === swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o pivy/gui/soqt_wrap.cpp interfaces/soqt.i === Generating pivy/coin_wrap.cpp for coin === swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o pivy/coin_wrap.cpp interfaces/coin.i running build_py creating build creating build/lib creating build/lib/pivy copying pivy/__init__.py -> build/lib/pivy copying pivy/sogui.py -> build/lib/pivy creating build/lib/pivy/gui copying pivy/gui/__init__.py -> build/lib/pivy/gui copying pivy/gui/soqt.py -> build/lib/pivy/gui copying pivy/coin.py -> build/lib/pivy running build_ext building 'gui._soqt' extension creating build/temp.linux-x86_64-2.6 creating build/temp.linux-x86_64-2.6/pivy creating build/temp.linux-x86_64-2.6/pivy/gui x86_64-pc-linux-gnu-gcc -pthread -DNDEBUG -march=core2 -O2 -pipe -fPIC -I/usr/include/python2.6 -c pivy/gui/soqt_wrap.cpp -o build/temp.linux-x86_64-2.6/pivy/gui/soqt_wrap.o -Iinterfaces -I/usr/include/Inventor/annex -D_REENTRANT -I/usr/include/qt4 -I/usr/include/qt4/Qt -DQT_DLL pivy/gui/soqt_wrap.cpp: In function ‘PyObject* _wrap_SbString_vsprintf(PyObject*, PyObject*)’: pivy/gui/soqt_wrap.cpp:9300: error: invalid array assignment error: command 'x86_64-pc-linux-gnu-gcc' failed with exit status 1 * ERROR: media-libs/pivy-0.3.0 failed: * Building failed * * Call stack: * ebuild.sh, line 55: Called src_compile * environment, line 3214: Called distutils_src_compile * environment, line 802: Called die * The specific snippet of code: * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed"; * * If you need support, post the output of 'emerge --info =media-libs/pivy-0.3.0', * the complete build log and the output of 'emerge -pqv =media-libs/pivy-0.3.0'. * The complete build log is located at '/var/log/portage/media-libs:pivy-0.3.0:20091106-095607.log'. * The ebuild environment file is located at '/var/tmp/portage/media-libs/pivy-0.3.0/temp/environment'. * S: '/var/tmp/portage/media-libs/pivy-0.3.0/work/Pivy-0.3.0' >>> Failed to emerge media-libs/pivy-0.3.0, Log file: >>> '/var/log/portage/media-libs:pivy-0.3.0:20091106-095607.log' ##################### Portage 2.1.7.3 (default/linux/amd64/10.0, gcc-4.4.2, glibc-2.11-r0, 2.6.31-gentoo-r4 x86_64) ================================================================= System uname: Linux-2.6.31-gentoo-r4-x86_64-Intel-R-_Core-TM-2_Duo_CPU_P9700_@_2.80GHz-with-gentoo-2.0.1 Timestamp of tree: Fri, 06 Nov 2009 08:00:20 +0000 app-shells/bash: 4.0_p35 dev-java/java-config: 2.1.9-r1 dev-lang/python: 2.6.4, 3.1.1-r1 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.5.2-r1 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.8.5-r3, 1.9.6-r2, 1.10.2, 1.11 sys-devel/binutils: 2.20 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /etc/X11/Sessions/awesome /etc/X11/Sessions/dwm /etc/X11/xorg.conf /etc/apache2/httpd.conf /etc/conf.d/hwclock /etc/conf.d/keymaps /etc/fstab /etc/make.conf /etc/xdg/openbox/autostart.sh /etc/xdg/openbox/menu.xml /etc/xdg/openbox/rc.xml /etc/xdg/openbox/start /usr/share/X11/xkb /usr/share/xsessions/openbox.desktop /var/bind /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/eselect/postgresql /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=core2 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="de_DE.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="de en vi" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/4Pane /usr/portage/local/layman/devnull /usr/portage/local/layman/gnome /usr/portage/local/layman/ibormuth /usr/portage/local/layman/java-overlay /usr/portage/local/layman/portato /usr/portage/local/layman/pro-audio /usr/portage/local/layman/scarabeus /usr/portage/local/layman/science /usr/portage/local/layman/xmw /usr/portage/local/local-overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="7zip X a52 aac aalib accessibility acl acpi adns afs aim alsa amd64 ao apache2 ass atm audio audiofile avahi bash-completion beagle berkdb bidi bluetooth bzip2 cairo caps cdda cdio cdparanoia cdr cgi cjk cli clisp consolekit cracklib crypt cscope css csv cups curl curlwrappers cvs dbus dc1394 dga dhcpcd dia dirac directfb dmx dri dts dv dvd dvdr dvi emacs enca encode enscript erandom exif expat extras faac faad fam fastcgi fbcon ffmpeg firefox flac flash fortran ftp fuse gcj gd gdbm geoip ggi gif gimp git glib gmp gnome gnome-keyring gnutls gphoto2 gpm graphviz gs gstreamer gtk gzip hal hash hddtemp highlight httpd iconv icq icu idn ieee1394 imagemagick imap imlib ipv6 jabber jack java java6 javascript jingle joystick jpeg jpeg2k kerberos lame lapack latex lcms ldap libcaca libwww live logrotate lua lzo mad maildir matroska md5sum memlimit mhash midi mikmod mime mjpeg mmap mmx mmxext mng mono motif mp3 mp4 mpeg mplayer msn mudflap mule multilib musepack mysql nas nautilus ncurses network networkmanager nfs nls nptl nptlonly nsplugin nvidia ogg ogg123 openal openexr opengl openmp oss pam pcmcia pcre pdf perl php pic pidgin png posix postgres ppds ps pulseaudio python qt3support qt4 quicktime radio rar raw rdesktop readline reflection rss rtsp ruby samba sasl savedconfig schroedinger sdl sdl-image session sip slang slp smp soap sockets sox spamassassin speex spell spl sqlite sse sse2 ssl stream stun subversion svg swat sysfs syslog sysvipc tcl tcpd theora threads tidy tiff timidity tk tokenizer truetype ucs2 udev unicode urandom usb userlocales v4l v4l2 vcd vhosts video vim-syntax vlc vlm vnc vorbis wav wavpack webkit wifi wma wmf wxwidgets x264 xattr xcb xcomposite xft xinerama xinetd xml xmlrpc xorg xpm xprint xscreensaver xsl xulrunner xv xvid xvmc yahoo zip zlib zsh-completion" ALSA_CARDS="hda_intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation php5 proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" APACHE2_MPMS="worker" CAMERAS="canon" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de en vi" USERLAND="GNU" VIDEO_CARDS="nv nvidia vesa fbdev vga vmware" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #6) > Checking for SWIG version... 1.3.40 > Warning: Pivy has only been tested with the following SWIG versions: 1.3.25. > Checking for coin-config... '/usr/bin/coin-config' > Coin version... 2.4.5 > Checking for Coin features... 3ds import vrml97 sound threads > Checking for soqt-config... '/usr/bin/soqt-config' > Checking for soqt version... 1.4.1 > Checking for soxt-config... not found. > Checking for sogtk-config... not found. > Checking for sowin-config... not found. > Preparing Inventor headers: Inventor/SbDPRotation.h Inventor/SbBox3f.h > Inventor/SbVec2d.h Inventor/SbVec2s.h Inventor/SbColor4f.h Inventor/SbMatrix.h > Inventor/SbName.h Inventor/SbBox2f.h Inventor/SbBox3s.h Inventor/SbVec3s.h > Inventor/SbTime.h Inventor/SbVec3f.h Inventor/SoPath.h > Inventor/SbViewportRegion.h Inventor/SbRotation.h Inventor/SbBox2s.h > Inventor/SoType.h Inventor/SbXfBox3f.h Inventor/SoOffscreenRenderer.h > Inventor/SbVec2f.h Inventor/SbString.h Inventor/SbColor.h Inventor/SbVec4f.h > Inventor/SbDPMatrix.h Inventor/SbVec4d.h Inventor/SbPlane.h Inventor/SbVec3d.h > Inventor/SoNodeKitPath.h Inventor/SoInput.h Inventor/SbViewVolume.h > Inventor/SbDPPlane.h Inventor/SbBox2d.h Inventor/SbImage.h > Inventor/engines/SoEngine.h Inventor/fields/SoMFVec3f.h > Inventor/fields/SoMFBool.h Inventor/fields/SoMFEngine.h > Inventor/fields/SoFieldContainer.h Inventor/fields/SoMFVec4f.h > Inventor/fields/SoMFMatrix.h Inventor/fields/SoSFInt32.h > Inventor/fields/SoSFPath.h Inventor/fields/SoSFUInt32.h > Inventor/fields/SoSFUShort.h Inventor/fields/SoField.h > Inventor/fields/SoMFRotation.h Inventor/fields/SoSFMatrix.h > Inventor/fields/SoSFName.h Inventor/fields/SoSFString.h > Inventor/fields/SoSFTime.h Inventor/fields/SoMFPath.h > Inventor/fields/SoSFVec3f.h Inventor/fields/SoMFNode.h > Inventor/fields/SoSFRotation.h Inventor/fields/SoSFPlane.h > Inventor/fields/SoMFPlane.h Inventor/fields/SoMFTime.h > Inventor/fields/SoSFImage.h Inventor/fields/SoMFInt32.h > Inventor/fields/SoMFFloat.h Inventor/fields/SoMFString.h > Inventor/fields/SoMFVec2f.h Inventor/fields/SoSFNode.h > Inventor/fields/SoSFEnum.h Inventor/fields/SoSFImage3.h > Inventor/fields/SoMFUShort.h Inventor/fields/SoSFVec4f.h > Inventor/fields/SoMFName.h Inventor/fields/SoSFVec2f.h > Inventor/fields/SoMField.h Inventor/fields/SoSFBool.h > Inventor/fields/SoSFShort.h Inventor/fields/SoMFUInt32.h > Inventor/fields/SoMFEnum.h Inventor/fields/SoSFTrigger.h > Inventor/fields/SoSFFloat.h Inventor/fields/SoMFShort.h > Inventor/fields/SoSFColor.h Inventor/fields/SoSFEngine.h > Inventor/fields/SoMFColor.h Inventor/draggers/SoDragger.h > Inventor/elements/SoDiffuseColorElement.h Inventor/elements/SoLazyElement.h > Inventor/misc/SoBase.h Inventor/collision/SoIntersectionDetectionAction.h > Inventor/lists/SbStringList.h Inventor/lists/SoFieldList.h > Inventor/lists/SoEngineList.h Inventor/lists/SbPList.h > Inventor/lists/SoDetailList.h Inventor/lists/SoEngineOutputList.h > Inventor/lists/SoTypeList.h Inventor/lists/SoBaseList.h > Inventor/lists/SoActionMethodList.h Inventor/lists/SbVec3fList.h > Inventor/lists/SbIntList.h Inventor/lists/SoPickedPointList.h > Inventor/lists/SoPathList.h Inventor/lists/SoNodeList.h > Inventor/nodekits/SoBaseKit.h Inventor/sensors/SoDataSensor.h > Inventor/sensors/SoAlarmSensor.h Inventor/sensors/SoIdleSensor.h > Inventor/sensors/SoTimerSensor.h Inventor/sensors/SoOneShotSensor.h > Inventor/sensors/SoTimerQueueSensor.h Inventor/sensors/SoDelayQueueSensor.h > Inventor/sensors/SoPathSensor.h Inventor/sensors/SoSensor.h > Inventor/sensors/SoFieldSensor.h Inventor/sensors/SoNodeSensor.h > Inventor/actions/SoGLRenderAction.h Inventor/actions/SoCallbackAction.h > Inventor/nodes/SoCallback.h Inventor/nodes/SoEventCallback.h > Inventor/nodes/SoSelection.h Inventor/Qt/SoQtRenderArea.h Inventor/Qt/SoQt.h. > === Generating pivy/gui/soqt_wrap.cpp for soqt === > swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall > -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o > pivy/gui/soqt_wrap.cpp interfaces/soqt.i > === Generating pivy/coin_wrap.cpp for coin === > swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall > -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o > pivy/coin_wrap.cpp interfaces/coin.i > running build_py > creating build > creating build/lib > creating build/lib/pivy > copying pivy/__init__.py -> build/lib/pivy > copying pivy/sogui.py -> build/lib/pivy > creating build/lib/pivy/gui > copying pivy/gui/__init__.py -> build/lib/pivy/gui > copying pivy/gui/soqt.py -> build/lib/pivy/gui > copying pivy/coin.py -> build/lib/pivy > running build_ext > building 'gui._soqt' extension > creating build/temp.linux-x86_64-2.6 > creating build/temp.linux-x86_64-2.6/pivy > creating build/temp.linux-x86_64-2.6/pivy/gui > x86_64-pc-linux-gnu-gcc -pthread -DNDEBUG -march=core2 -O2 -pipe -fPIC > -I/usr/include/python2.6 -c pivy/gui/soqt_wrap.cpp -o > build/temp.linux-x86_64-2.6/pivy/gui/soqt_wrap.o -Iinterfaces > -I/usr/include/Inventor/annex -D_REENTRANT -I/usr/include/qt4 > -I/usr/include/qt4/Qt -DQT_DLL > pivy/gui/soqt_wrap.cpp: In function ‘PyObject* > _wrap_SbString_vsprintf(PyObject*, PyObject*)’: > pivy/gui/soqt_wrap.cpp:9300: error: invalid array assignment > error: command 'x86_64-pc-linux-gnu-gcc' failed with exit status 1 > * ERROR: media-libs/pivy-0.3.0 failed: > * Building failed > * > * Call stack: > * ebuild.sh, line 55: Called src_compile > * environment, line 3214: Called distutils_src_compile > * environment, line 802: Called die > * The specific snippet of code: > * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || > die "Building failed"; > * > * If you need support, post the output of 'emerge --info > =media-libs/pivy-0.3.0', > * the complete build log and the output of 'emerge -pqv > =media-libs/pivy-0.3.0'. > * The complete build log is located at > '/var/log/portage/media-libs:pivy-0.3.0:20091106-095607.log'. > * The ebuild environment file is located at > '/var/tmp/portage/media-libs/pivy-0.3.0/temp/environment'. > * S: '/var/tmp/portage/media-libs/pivy-0.3.0/work/Pivy-0.3.0' > >>> Failed to emerge media-libs/pivy-0.3.0, Log file: > >>> '/var/log/portage/media-libs:pivy-0.3.0:20091106-095607.log' > ##################### > Portage 2.1.7.3 (default/linux/amd64/10.0, gcc-4.4.2, glibc-2.11-r0, > 2.6.31-gentoo-r4 x86_64) > ================================================================= > System uname: > Linux-2.6.31-gentoo-r4-x86_64-Intel-R-_Core-TM-2_Duo_CPU_P9700_@_2.80GHz-with-gentoo-2.0.1 > Timestamp of tree: Fri, 06 Nov 2009 08:00:20 +0000 > app-shells/bash: 4.0_p35 > dev-java/java-config: 2.1.9-r1 > dev-lang/python: 2.6.4, 3.1.1-r1 > dev-util/cmake: 2.6.4-r3 > sys-apps/baselayout: 2.0.1 > sys-apps/openrc: 0.5.2-r1 > sys-apps/sandbox: 2.2 > sys-devel/autoconf: 2.13, 2.63-r1 > sys-devel/automake: 1.8.5-r3, 1.9.6-r2, 1.10.2, 1.11 > sys-devel/binutils: 2.20 > sys-devel/gcc-config: 1.4.1 > sys-devel/libtool: 2.2.6a > virtual/os-headers: 2.6.30-r1 > ACCEPT_KEYWORDS="amd64 ~amd64" > CBUILD="x86_64-pc-linux-gnu" > CFLAGS="-march=core2 -O2 -pipe" > CHOST="x86_64-pc-linux-gnu" > CONFIG_PROTECT="/etc /etc/X11/Sessions/awesome /etc/X11/Sessions/dwm > /etc/X11/xorg.conf /etc/apache2/httpd.conf /etc/conf.d/hwclock > /etc/conf.d/keymaps /etc/fstab /etc/make.conf /etc/xdg/openbox/autostart.sh > /etc/xdg/openbox/menu.xml /etc/xdg/openbox/rc.xml /etc/xdg/openbox/start > /usr/share/X11/xkb /usr/share/xsessions/openbox.desktop /var/bind > /var/lib/hsqldb" > CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ > /etc/eselect/postgresql /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release > /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ > /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo > /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d > /etc/texmf/web2c /etc/udev/rules.d" > CXXFLAGS="-march=core2 -O2 -pipe" > DISTDIR="/usr/portage/distfiles" > FEATURES="assume-digests distlocks fixpackages news parallel-fetch > protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" > GENTOO_MIRRORS="http://distfiles.gentoo.org > http://distro.ibiblio.org/pub/linux/distributions/gentoo" > LANG="de_DE.UTF-8" > LDFLAGS="-Wl,-O1" > LINGUAS="de en vi" > MAKEOPTS="-j3" > PKGDIR="/usr/portage/packages" > PORTAGE_CONFIGROOT="/" > PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress > --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles > --exclude=/local --exclude=/packages" > PORTAGE_TMPDIR="/var/tmp" > PORTDIR="/usr/portage" > PORTDIR_OVERLAY="/usr/portage/local/layman/4Pane > /usr/portage/local/layman/devnull /usr/portage/local/layman/gnome > /usr/portage/local/layman/ibormuth /usr/portage/local/layman/java-overlay > /usr/portage/local/layman/portato /usr/portage/local/layman/pro-audio > /usr/portage/local/layman/scarabeus /usr/portage/local/layman/science > /usr/portage/local/layman/xmw /usr/portage/local/local-overlay" > SYNC="rsync://rsync.gentoo.org/gentoo-portage" > USE="7zip X a52 aac aalib accessibility acl acpi adns afs aim alsa amd64 ao > apache2 ass atm audio audiofile avahi bash-completion beagle berkdb bidi > bluetooth bzip2 cairo caps cdda cdio cdparanoia cdr cgi cjk cli clisp > consolekit cracklib crypt cscope css csv cups curl curlwrappers cvs dbus dc1394 > dga dhcpcd dia dirac directfb dmx dri dts dv dvd dvdr dvi emacs enca encode > enscript erandom exif expat extras faac faad fam fastcgi fbcon ffmpeg firefox > flac flash fortran ftp fuse gcj gd gdbm geoip ggi gif gimp git glib gmp gnome > gnome-keyring gnutls gphoto2 gpm graphviz gs gstreamer gtk gzip hal hash > hddtemp highlight httpd iconv icq icu idn ieee1394 imagemagick imap imlib ipv6 > jabber jack java java6 javascript jingle joystick jpeg jpeg2k kerberos lame > lapack latex lcms ldap libcaca libwww live logrotate lua lzo mad maildir > matroska md5sum memlimit mhash midi mikmod mime mjpeg mmap mmx mmxext mng mono > motif mp3 mp4 mpeg mplayer msn mudflap mule multilib musepack mysql nas > nautilus ncurses network networkmanager nfs nls nptl nptlonly nsplugin nvidia > ogg ogg123 openal openexr opengl openmp oss pam pcmcia pcre pdf perl php pic > pidgin png posix postgres ppds ps pulseaudio python qt3support qt4 quicktime > radio rar raw rdesktop readline reflection rss rtsp ruby samba sasl savedconfig > schroedinger sdl sdl-image session sip slang slp smp soap sockets sox > spamassassin speex spell spl sqlite sse sse2 ssl stream stun subversion svg > swat sysfs syslog sysvipc tcl tcpd theora threads tidy tiff timidity tk > tokenizer truetype ucs2 udev unicode urandom usb userlocales v4l v4l2 vcd > vhosts video vim-syntax vlc vlm vnc vorbis wav wavpack webkit wifi wma wmf > wxwidgets x264 xattr xcb xcomposite xft xinerama xinetd xml xmlrpc xorg xpm > xprint xscreensaver xsl xulrunner xv xvid xvmc yahoo zip zlib zsh-completion" > ALSA_CARDS="hda_intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare > dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw > multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias > auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file > authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user > autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires > ext_filter file_cache filter headers ident imagemap include info log_config > logio mem_cache mime mime_magic negotiation php5 proxy proxy_ajp roxy_balancer > proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir > usertrack vhost_alias" APACHE2_MPMS="worker" CAMERAS="canon" ELIBC="glibc" > INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" > LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses > text" LINGUAS="de en vi" USERLAND="GNU" VIDEO_CARDS="nv nvidia vesa fbdev vga > vmware" > Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, > PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS Oke, I send this bug report to the people of pivy so i can hear what's going wrong here. Roelof
Hi Justin I was made aware of this issue by Roleof I am one of the maintainers for Pivy, SoQt and Coin. I am also a long time Gentoo user. I see that the versions available in Gentoo for SoQt and Coin needs maintainers. If you are interested in maintainers for these packages, I would like to offer my services. Tom Fredrik
Created attachment 209428 [details, diff] patch for pivy so i can build
(In reply to comment #9) > Created an attachment (id=209428) [details] > patch for pivy so i can build > Hello Justin. Can you try this patch. It's provided by Tom. Roelof
(In reply to comment #10) > (In reply to comment #9) > > Created an attachment (id=209428) [details] [details] > > patch for pivy so i can build > > > > Hello Justin. > > Can you try this patch. > It's provided by Tom. > > Roelof > Hello Tom. Why not also a maintainer of Pivy. Roelof
(In reply to comment #8) > Hi Justin > > I was made aware of this issue by Roleof > > I am one of the maintainers for Pivy, SoQt and Coin. I am also a long time > Gentoo user. > > I see that the versions available in Gentoo for SoQt and Coin needs > maintainers. > If you are interested in maintainers for these packages, I would like to offer > my services. > > Tom Fredrik > Hi Tom, since you are no gentoo dev, you cannot directly maintain the ebuilds in gentoo main tree, but you could (maybe with the help of Roelof, who offered to do the ebuild part) create ebuilds and fix bugs and ask some gentoo dev to proxy the work into the main tree. If you find no other dev, and you (both) do proper work, i might offer to do the proxy part.
(In reply to comment #11) > (In reply to comment #10) > Hello Tom. > > Why not also a maintainer of Pivy. Sorry about the ambiguity, I didn't intend to not offer to maintain Pivy, I only meant to imply that SoQt and Coin are the only packages that are listed as maintainers wanted.
(In reply to comment #12) > Hi Tom, > > since you are no gentoo dev, you cannot directly maintain the ebuilds in gentoo > main tree, but you could (maybe with the help of Roelof, who offered to do the > ebuild part) create ebuilds and fix bugs and ask some gentoo dev to proxy the > work into the main tree. If you find no other dev, and you (both) do proper > work, i might offer to do the proxy part. Hi Thomas I'll do it the way you think is more convenient :-) Sorry, I haven't been active in the Gentoo community for a long while, so I'm a bit out of touch with the processes. I hope I can bother you with some questions. If I'm not mistaken the core gentoo repos is still a subversion repository? No plans for changing to a distributed model, where you can simply sign off patches? What is your recommended model for doing work like this, simply just submit a bugreport, and attach a new ebuild or patch? How would we be notified about issues regarding the specific ebuilds we are caring for? Tom Fredrik
(In reply to comment #14) > (In reply to comment #12) > > Hi Tom, > > > > since you are no gentoo dev, you cannot directly maintain the ebuilds in gentoo > > main tree, but you could (maybe with the help of Roelof, who offered to do the > > ebuild part) create ebuilds and fix bugs and ask some gentoo dev to proxy the > > work into the main tree. If you find no other dev, and you (both) do proper > > work, i might offer to do the proxy part. > > Hi Thomas > > I'll do it the way you think is more convenient :-) > > Sorry, I haven't been active in the Gentoo community for a long while, so I'm a > bit out of touch with the processes. I hope I can bother you with some > questions. > > If I'm not mistaken the core gentoo repos is still a subversion repository? > No plans for changing to a distributed model, where you can simply sign off > patches? > What is your recommended model for doing work like this, simply just submit a > bugreport, and attach a new ebuild or patch? > How would we be notified about issues regarding the specific ebuilds we are > caring for? > > Tom Fredrik > Hello Tom There are a lot of packages that need a maintainer. If you want you may also write the ebuilds yourself. My thoughts are that all three packages come from your company so If there are problems you are in my opion the best person for the job. Also I never have learned to write patches so If i write the ebuilds and there are problems I allways need your help. If that is no problem with you, it's my offer to write the ebuilds and let you solve the problems with the packages. Roelof
(In reply to comment #14) > If I'm not mistaken the core gentoo repos is still a subversion repository? No, its still cvs. > No plans for changing to a distributed model, where you can simply sign off > patches? There are plans, but current version of git cannot handle the big amount of data in our repo in a sane way. > What is your recommended model for doing work like this, simply just submit a > bugreport, and attach a new ebuild or patch? I prefer using the sunrise overlay with the same policy as for ebuilds, which got into the overlay, only difference that the ebuilds for main tree go into portage-review dir. > How would we be notified about issues regarding the specific ebuilds we are > caring for? Those, who do the work, are marked as maintainer in the metadata.xml of the ebuilds, so you (or Roelof) would get the bug in bugzilla assigned with the others in CC.
(In reply to comment #16) > (In reply to comment #14) > > If I'm not mistaken the core gentoo repos is still a subversion repository? > > No, its still cvs. > > > No plans for changing to a distributed model, where you can simply sign off > > patches? > > There are plans, but current version of git cannot handle the big amount of > data in our repo in a sane way. > > > What is your recommended model for doing work like this, simply just submit a > > bugreport, and attach a new ebuild or patch? > > I prefer using the sunrise overlay with the same policy as for ebuilds, which > got into the overlay, only difference that the ebuilds for main tree go into > portage-review dir. > > > How would we be notified about issues regarding the specific ebuilds we are > > caring for? > > Those, who do the work, are marked as maintainer in the metadata.xml of the > ebuilds, so you (or Roelof) would get the bug in bugzilla assigned with the > others in CC. > Oke, And how does it work as I write the ebuilds and Tom does the patches and solving the configure problems. and you are the proxy. Roelof
(In reply to comment #17) > (In reply to comment #16) > > (In reply to comment #14) > > > If I'm not mistaken the core gentoo repos is still a subversion repository? > > > > No, its still cvs. > > > > > No plans for changing to a distributed model, where you can simply sign off Hellle tman, The problem is that Gentoo has a too old version of SoQt. Tom has voluteerd to write new Ebuilds for coin and soqt so I have to wait till he has finished his builds. Roelof > > > patches? > > > > There are plans, but current version of git cannot handle the big amount of > > data in our repo in a sane way. > > > > > What is your recommended model for doing work like this, simply just submit a > > > bugreport, and attach a new ebuild or patch? > > > > I prefer using the sunrise overlay with the same policy as for ebuilds, which > > got into the overlay, only difference that the ebuilds for main tree go into > > portage-review dir. > > > > > How would we be notified about issues regarding the specific ebuilds we are > > > caring for? > > > > Those, who do the work, are marked as maintainer in the metadata.xml of the > > ebuilds, so you (or Roelof) would get the bug in bugzilla assigned with the > > others in CC. > > > Oke, > And how does it work as I write the ebuilds and Tom does the patches and > solving the configure problems. and you are the proxy. > Roelof
Created attachment 211331 [details] revised to add epatching routine -- patch needs fixing as well
Created attachment 211332 [details, diff] strip junk from patch so it works properly fixes patching failure due to extraneous characters in the original
with these changes it still fails :( .. brief tail of output === Generating pivy/coin_wrap.cpp for coin === swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o pivy/coin_wrap.cpp interfaces/coin.i running build_py creating build creating build/lib creating build/lib/pivy copying pivy/__init__.py -> build/lib/pivy copying pivy/sogui.py -> build/lib/pivy creating build/lib/pivy/gui copying pivy/gui/__init__.py -> build/lib/pivy/gui copying pivy/gui/soqt.py -> build/lib/pivy/gui copying pivy/coin.py -> build/lib/pivy running build_ext building 'gui._soqt' extension creating build/temp.linux-i686-2.6 creating build/temp.linux-i686-2.6/pivy creating build/temp.linux-i686-2.6/pivy/gui i686-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=athlon-xp -pipe -fPIC -I/usr/include/python2.6 -c pivy/gui/soqt_wrap.cpp -o build/temp.linux-i686-2.6/pivy/gui/soqt_wrap.o -Iinterfaces -I/usr/include/Inventor/annex -D_REENTRANT -I/usr/include/qt4 -I/usr/include/qt4/Qt -DQT_DLL pivy/gui/soqt_wrap.cpp: In function 'PyObject* _wrap_SbDictApplyFunc(PyObject*, PyObject*)': pivy/gui/soqt_wrap.cpp:5117: error: functional cast expression list treated as compound expression pivy/gui/soqt_wrap.cpp:5117: error: invalid cast to function type 'void ()(SbDictKeyType, void*)' pivy/gui/soqt_wrap.cpp: In function 'PyObject* _wrap_SbDictApplyDataFunc(PyObject*, PyObject*)': pivy/gui/soqt_wrap.cpp:5160: error: functional cast expression list treated as compound expression pivy/gui/soqt_wrap.cpp:5160: error: invalid cast to function type 'void ()(SbDictKeyType, void*, void*)' pivy/gui/soqt_wrap.cpp: In function 'PyObject* _wrap_SbDictHashingFunc(PyObject*, PyObject*)': pivy/gui/soqt_wrap.cpp:5190: error: invalid cast to function type 'SbDictKeyType ()(SbDictKeyType)' error: command 'i686-pc-linux-gnu-gcc' failed with exit status 1 * ERROR: sci-misc/pivy-0.3.0 failed: * Building failed * * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3194: Called distutils_src_compile * environment, line 790: Called die * The specific snippet of code: * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed"; * * If you need support, post the output of 'emerge --info =sci-misc/pivy-0.3.0', * the complete build log and the output of 'emerge -pqv =sci-misc/pivy-0.3.0'. * This ebuild is from an overlay named 'personal-derk': '/home/derk/portage/' * The complete build log is located at '/var/tmp/portage/sci-misc/pivy-0.3.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sci-misc/pivy-0.3.0/temp/environment'. * S: '/var/tmp/portage/sci-misc/pivy-0.3.0/work/Pivy-0.3.0' Can anybody tell me what to look at next .. I am using a newer coin-3.1.0 (slight mode to new ebuild above)
(In reply to comment #21) > with these changes it still fails :( .. brief tail of output > > > === Generating pivy/coin_wrap.cpp for coin === > > swig -w302,306,307,312,389,361,362,467,503,509,510 -c++ -python -includeall > -modern -D__PIVY__ -I. -Ifake_headers -I/usr/include -Iinterfaces -o > pivy/coin_wrap.cpp interfaces/coin.i > running build_py > creating build > creating build/lib > creating build/lib/pivy > copying pivy/__init__.py -> build/lib/pivy > copying pivy/sogui.py -> build/lib/pivy > creating build/lib/pivy/gui > copying pivy/gui/__init__.py -> build/lib/pivy/gui > copying pivy/gui/soqt.py -> build/lib/pivy/gui > copying pivy/coin.py -> build/lib/pivy > running build_ext > building 'gui._soqt' extension > creating build/temp.linux-i686-2.6 > creating build/temp.linux-i686-2.6/pivy > creating build/temp.linux-i686-2.6/pivy/gui > i686-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=athlon-xp -pipe -fPIC > -I/usr/include/python2.6 -c pivy/gui/soqt_wrap.cpp -o > build/temp.linux-i686-2.6/pivy/gui/soqt_wrap.o -Iinterfaces > -I/usr/include/Inventor/annex -D_REENTRANT -I/usr/include/qt4 > -I/usr/include/qt4/Qt -DQT_DLL > pivy/gui/soqt_wrap.cpp: In function 'PyObject* _wrap_SbDictApplyFunc(PyObject*, > PyObject*)': > pivy/gui/soqt_wrap.cpp:5117: error: functional cast expression list treated as > compound expression > pivy/gui/soqt_wrap.cpp:5117: error: invalid cast to function type 'void > ()(SbDictKeyType, void*)' > pivy/gui/soqt_wrap.cpp: In function 'PyObject* > _wrap_SbDictApplyDataFunc(PyObject*, PyObject*)': > pivy/gui/soqt_wrap.cpp:5160: error: functional cast expression list treated as > compound expression > pivy/gui/soqt_wrap.cpp:5160: error: invalid cast to function type 'void > ()(SbDictKeyType, void*, void*)' > pivy/gui/soqt_wrap.cpp: In function 'PyObject* > _wrap_SbDictHashingFunc(PyObject*, PyObject*)': > pivy/gui/soqt_wrap.cpp:5190: error: invalid cast to function type > 'SbDictKeyType ()(SbDictKeyType)' > error: command 'i686-pc-linux-gnu-gcc' failed with exit status 1 > * ERROR: sci-misc/pivy-0.3.0 failed: > * Building failed > * > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 3194: Called distutils_src_compile > * environment, line 790: Called die > * The specific snippet of code: > * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || > die "Building failed"; > * > * If you need support, post the output of 'emerge --info > =sci-misc/pivy-0.3.0', > * the complete build log and the output of 'emerge -pqv =sci-misc/pivy-0.3.0'. > * This ebuild is from an overlay named 'personal-derk': '/home/derk/portage/' > * The complete build log is located at > '/var/tmp/portage/sci-misc/pivy-0.3.0/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/sci-misc/pivy-0.3.0/temp/environment'. > * S: '/var/tmp/portage/sci-misc/pivy-0.3.0/work/Pivy-0.3.0' > > Can anybody tell me what to look at next .. I am using a newer coin-3.1.0 > (slight mode to new ebuild above) > Hello , What we need is a newer version of SoqT. That will be build by another person. Therefore I can't make a working ebuild of Pivy. Roelof
Since the most recent release from Coin3D for media-libs/SoQt is version 1.4.1 for which an ebuild is in the main portage tree what is the issue?
(In reply to comment #23) > Since the most recent release from Coin3D for media-libs/SoQt is version 1.4.1 > for which an ebuild is in the main portage tree what is the issue? > The issue is that the 1.4.1 version of SoQT is too old. A person which developing SoQt and Coin said that and he's willing to make new ebuilds for that packages. So I have to wait till he has finisched that. Roelof
Created attachment 212767 [details] Version bump to 0.5 revision 592 New Ebuild. Depencies can be found at science overlay.
(In reply to comment #25) > Created an attachment (id=212767) [details] > Version bump to 0.5 revision 592 > > New Ebuild. > Depencies can be found at science overlay. > Hello, Coin can now be found at the main tree Roelof
Created attachment 213196 [details] Changing some depencies
(In reply to comment #27) > Created an attachment (id=213196) [details] > Changing some depencies > Who came up with the tar.gz hosting on omploader? Why is there junk 'build' folder in it? I can't trust it! Why is it named this way - svn version is at 765 since 6 months! I found old code in the omped source! Isn't following link sufficient enough? http://pivy.coin3d.org/download/snapshot/releases/daily/Pivy-latest.tar.gz Please adapt it!
(In reply to comment #28) > (In reply to comment #27) > > Created an attachment (id=213196) [details] [details] > > Changing some depencies > > > Who came up with the tar.gz hosting on omploader? Why is there junk 'build' > folder in it? > I can't trust it! > > Why is it named this way - svn version is at 765 since 6 months! > I found old code in the omped source! > > Isn't following link sufficient enough? > http://pivy.coin3d.org/download/snapshot/releases/daily/Pivy-latest.tar.gz Please don't ;-) To be honest I don't know if that link is properly updated anymore, I'll check that when I'm back at work on Monday. Since all our sources are kept in Mercurial repositories, that is the authoritative source. The correct link for the latest development version of Pivy is always http://hg.sim.no/Pivy/default/archive/tip.tar.bz2 I've added some gentoo specific fixes there which are not present in the subversion sources, which we abandoned last autumn.
(In reply to comment #29) > (In reply to comment #28) > > (In reply to comment #27) > > > Created an attachment (id=213196) [details] [details] [details] > > > Changing some depencies > > > > > Who came up with the tar.gz hosting on omploader? Why is there junk 'build' > > folder in it? > > I can't trust it! > > > > Why is it named this way - svn version is at 765 since 6 months! > > I found old code in the omped source! > > > > Isn't following link sufficient enough? > > http://pivy.coin3d.org/download/snapshot/releases/daily/Pivy-latest.tar.gz > > Please don't ;-) > > To be honest I don't know if that link is properly updated anymore, I'll check > that when I'm back at work on Monday. Confirmed. It stopped working when we moved from Subversion.
It seems that the C++ source that should be created by swig already exist in the provided source package. Can we get a clean source package for pivy?
(In reply to comment #31) > It seems that the C++ source that should be created by swig already exist in > the provided source package. Can we get a clean source package for pivy? > Could you please explain what you are referring to? - An example of such a file would be great. I looked briefly, and I cannot see that I found any such files.
(In reply to comment #32) > Could you please explain what you are referring to? - An example of such a file > would be great. when i build pivy the output contains this warnig, and the resulting package doe not work: === pivy/gui/soqt_wrap.cpp for pivy.gui.soqt already exists! === === pivy/coin_wrap.cpp for pivy.coin already exists! == if I add the source configure call src_configure() { python setup.py clean } to the ebuild script, the above files are removed, and then recreated using the local coin and soqt using the local swig, and the resulting build actually functions correctly.
Created attachment 256506 [details] cleaned swig-wrappers Thanks for mentioning that the SWIG-wrappers were not cleaned. Adding the 'clean' action helped for making it work. The the attached ebuild for changes: 1.) added swig to DEPEND 2.) run 'clean' in src_prepare
Understood why this was going wrong, the package you are using is not from the official repository. Just added a snapshot, which can be used: http://hg.sim.no/Pivy/default/archive/pivy-20101207.tar.bz2
Thanks. But it seems like pivy (tested with the old snapshot, not the one you provided) does NOT work with swig-1.3.40, but only with 1.3.35. -- Problem is: the latter isn't in portage anymore. The problem with swig-1.3.40 I had is: Adding a SoSeparator to a SoGroup via "addChild" yields the error, that the first argument should be "SoGroup *". (I can't currently reproduce it due to a lack of time. Might do it tomorrow if needed)
I can understand what that is all about, seems some headers are not included properly, and SoSeparator is not behaving as a proper child of SoGroup. Anyway, I'm unfortunately not using gentoo as my primary platform at the moment, but when I was about half a year ago, all my testing was done on gentoo, so I'm surprised if this is the case with the snapshot provided. If you can confirm this is a problem, I'll have a go at emerge -uND world, but I'believe that's going to take a while.
In the main portage tree now as dev-python/pivy-0.5_alpha20110303 (snapshot).
