Hi, Please find attached ocs-2.3h.ebuild. OCS stands for "Opal Compiler Suite". Opal is a strongly typed, higher-order, strict, pure functional language, and as such can be classified alongside ML, Haskell, and other modern functional programming languages. However, the language also has a distinctive algebraic flavour in the tradition of languages such as CIP-L, Obj, and others. Opal uses gcc as wrapper for compilation. Homepage is: http://uebb.cs.tu-berlin.de/~opal/ I suggest dev-lang/ocs. Also, this ebuild can be compiled with support for X, TclTK, but no JAVA at the moment, because it's still alpha in ocs. Have fun, - Christian
Created attachment 28460 [details] ocs-2.3h.ebuild
Re-assign.
Created attachment 99943 [details] version bump and minor tweaks to the ebuild. At least for me it does not compile on a mostly stable Gentoo box.
Created attachment 101270 [details] ocs-2.3k.ebuild - some warnings because insecure DT_RUNPATH - version bump to 2.3k - some sandbox problems fixed (chown wanted to break out) TODO: - problems with insecure DT_RUNPATH warnings - java not tested - linking to the window-lib. doesn't work.
Christian, could you eventually overtake the maintainership for this ebuild? This way we might get it into portage some day ... Just curious: are you studing at the TU Berlin?
I can compile and install the ebuild from #4 without problems but I can not run oasys - oasysbin does not exist on my system. Just me or do you have the same problems? ~ $ oasys /usr/local/ocs/bin/oasys: line 58: /usr/local/ocs/bin/oasysbin: No such file or directory /usr/local/ocs/bin/oasys: line 58: exec: /usr/local/ocs/bin/oasysbin: cannot execute: No such file or directory ~ $ /usr/local/ocs/bin/oasys /usr/local/ocs/bin/oasys: line 58: /usr/local/ocs/bin/oasysbin: No such file or directory /usr/local/ocs/bin/oasys: line 58: exec: /usr/local/ocs/bin/oasysbin: cannot execute: No such file or directory
OK, my problem is "solved". By reading the ebuild I found out that oasys is not even build when the "tcl" USE is not set. In my opinion we should either tell the user this with an einfo or drop the tcl USE, add tcl to DEPEND and always build oasys. Is there a good reason why one might want to build ocs without oasys (in other words: is ocs usable at all without oasys)? Your comments are welcome.
(In reply to comment #7) > In my opinion we should either tell the user this with an einfo or drop the tcl > USE, add tcl to DEPEND and always build oasys. Is there a good reason why one > might want to build ocs without oasys (in other words: is ocs usable at all > without oasys)? Your comments are welcome. Yes it is, as oasys is just an interpreter for the ocs compiler. And about putting Opal into portage: I do not think that this is a good idea, since it is pretty much unmaintained, has an ugly patched own build system and probably does not build many arches other than x86. One could put it into an overlay though.
(In reply to comment #8) > And about putting Opal into portage: I do not think that this is a good idea, > since it is pretty much unmaintained, has an ugly patched own build system and > probably does not build many arches other than x86. > One could put it into an overlay though. > It does indeed not build on amd64 (I can post logs if someone is interested). Well, I though maybe a binary build (ocs-bin) would be a good idea (32-bit)? Could someone create such a thing? It would at least be a temporary solution for 64-bit systems (multi lib).
(In reply to comment #9) > (In reply to comment #8) > > And about putting Opal into portage: I do not think that this is a good idea, > > since it is pretty much unmaintained, has an ugly patched own build system and > > probably does not build many arches other than x86. > > One could put it into an overlay though. > > > > It does indeed not build on amd64 (I can post logs if someone is interested). Could please try including these patches someone created against the Makefiles and report back? http://opalix.freitagsrunde.org/debian-rep/ocs_2.3j-1.diff.gz
Created attachment 132044 [details] New ebuild for ocs-2.3j and support for the mentioned patch You need to unpack this patch to .../files/ocs-2.3j-extpatch.patch. As this patch is indicated as j-version, so the ebuild I based on is also for the j-version. Ebuild fails
Created attachment 132045 [details] build log adam@awi-laptop ~ $ sudo emerge --info Portage 2.1.3.9 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.20-gentoo-r8-b2 x86_64) ================================================================= System uname: 2.6.20-gentoo-r8-b2 x86_64 Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz Timestamp of tree: Mon, 17 Sep 2007 12:30:01 +0000 app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17-r1 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer multilib parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_GB.UTF-8" LINGUAS="pl en_GB en de" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_COMPRESS="bzip2" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/x4x-portage /usr/local/portage /usr/portage/local/layman/java-overlay /usr/portage/local/layman/java-gcj-overlay /usr/portage/local/layman/toolchain /usr/portage/local/layman/pro-audio /usr/portage/local/layman/science /usr/portage/local/layman/sunrise" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X X509 a52 aac aalib accessibility acl acpi alsa amd64 apache2 apm avi bash-completion berkdb bitmap-fonts bittorrent boo bzip2 c++ cairo cddb cdparanoia cdr cli cpudetection cracklib crypt cups curl d dbus dierectfb directfb divx dlloader dri dts dv dvd dvdnav dvdr dvdread emerald encode erandom exif fam fat fbcon ffmpeg firefox flac fortran gadu gdbm gdm gif glade glib glitz gmail gmedia gnome gnutls gpm gstreamer gtk hal iconv imagemagick iproute2 ipv6 ipw3945 isdnlog jabber java java5 jce jpeg kerberos kerbos krb4 ladspa lame ldap libcaca libnotify logrotate mad maildir mbox mhash midi mmap mmx mng mono mp3 mpeg mudflap musepack mysql ncurses nls nptl nptlonly nsplugin ntfs odbc odk ogg opengl openmp pam pcntl pcre perl pmu png posix postgres pppd python qt3support quicktime readline reflection reiserfs sbcl sdl session slang sndfile sockets sound sox spell spl sqlite sqlite3 sse sse2 ssl subversion svg sysvipc tagwriting tcl tcpd tetex threads threadsafe tiff tk truetype truetype-fonts type1-fonts unicode usb vcd vim vim-syntax vim-sytanx vim-with-x vorbis wavpack wireshark xine xml xorg xv xvid zlib" ALSA_CARDS="hda-intel usb-audio" 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" ELIBC="glibc" INPUT_DEVICES="evdev mouse keyboard synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="pl en_GB en de" USERLAND="GNU" VIDEO_CARDS="i810" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS I emerged with USE="latex" (shouldn't it actually be named tetex?)
(In reply to comment #11) > Created an attachment (id=132044) [edit] > New ebuild for use with this patch > > You need to unpack this patch to .../files/ocs-2.3j-extpatch.patch. > As this patch is indicated as j-version, so the ebuild I based on is also for > the j-version. > > Ebuild fails Retry with the k version. The patch will apply fine.
Created attachment 133861 [details] an binary ebuild derived from debian i386 version Well, it doesn't work. If there were a 64bit build it should, though. adam@laptop-awi ~/devel/opal $ oasys /usr/lib/ocs/ocs/bin/oasysbin: error while loading shared libraries: libtcl8.4.so.0: cannot open shared object file: No such file or directory I searched for some 32-bit tcl libraries, but there are none. no emul-linux-x86-tcl or analogue... Well, I believe I'd have to use Opalix. Is there really no amd64 binary package?
Created attachment 133863 [details] build log for ocs-2.3k with the patch The build failed. But with some other error.
I have a working (on x86) ebuild in my overlay. I can reproduce the same error with amd64, so ocs just does not compile on amd64. Don't bother trying. If you want to run it on 64 bit, compile it in a 32 bit chroot and build emulation packages or run it from there. There's a lot of docs how to do that. Installing compiled Debian packages or what not will not help this either.
(this is an automated message based on filtering criteria that matched this bug) 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. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
