As best I can tell (first-time Dylan and d2c user, so take this with a grain of salt) the gwydion-dylan ebuild only does an initial bootstrap on the first installation. After emerge d2c seemed to function but the make-dylan-app script was missing, and with some hand-holding from #dylan I found that some of the libraries in /usr/lib/dylan were missing as well. I was told that it looked like an initial bootstrap, and looking at the source tarball it appeared that it does a bootstrap if no existing d2c was found and a normal build if one exists. I guessed that a re-emerge would do the job and that looks correct. Assuming I understand what happened correctly, this is pretty confusing for those of us who don't yet know what we're doing, and Dylan probably doesn't need any more obscurity. :-) It would be helpful for those of us who are encountering d2c for the first time and don't understand its build system if the ebuild could automatically do two builds on a new emerge. If that is infeasible for some reason, perhaps the ebuild could print a message warning the user that a re-emerge is needed for a full installation. I doubt it's relevant since the hand-build behavior appeared to be the same, but I've included emerge --info output below. Dustin ----------------------------------------------------------------------- laurence@lindy ~ $ emerge --info Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-suspend2-r4-basic-06.01.24-01 i686) ================================================================= System uname: 2.6.13-suspend2-r4-basic-06.01.24-01 i686 Intel(R) Pentium(R) M processor 1.73GHz Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac aalib acl acpi alsa apache2 asf audiofile avi berkdb bitmap-fonts bzip2 cdparanoia cdr cli crypt cups curl dbus doc dri dvd dvdr eds emboss encode exif expat fam ffmpeg fftw flac foomaticdb fortran gcj gd gdbm gif glut gmp gnome gpm gtk gtk2 gtkhtml hal howl idn ieee1394 imagemagick imap imlib ipv6 isdnlog jack jpeg junit ladcca lcms ldap libg++ libwww mad maildir mikmod mng mozilla mp3 mpeg ncurses new-login nls nsplugin ogg oggvorbis opengl pam pcmcia pcre pdflib perl png postfix ppds pppd python quicktime readline reflection scanner sdl session speex spell spl ssl svg tcltk tcpd theora tiff truetype truetype-fonts type1-fonts udev usb v4l vcd vhosts vorbis wifi win32codecs wmf xine xml2 xmms xorg xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
(In reply to comment #0) same here. the initial bootstrap is splitted in some stages, and if is no d2c on the system mindy is used. if there is d2c on the system, the first stages are not neccessary. So u once fishished the first install, d2c is on your system an can be used to make another installation (and this works fine). (i'am dylan beginner too)
Hello, I have not been able to reproduce this bug .... But i'd be happy to investigate further, if you give me some help. First at all, notice there exist 2 gwydion-dylan packages in the tree. The gwydion-dylan source package and the -bin version. The -bin version is used to bootstrap the sources and make a regular build. Therefore the usual procedure is to get installed gd-bin and with this _minimal_ set, to get gwydion-dylan installed, which is the version intended to use, and then you can safely uninstall the -bin version if you want. This (of course) is all done through an 'emerge gwydion-dylan' automatically. If you are sure of using the right package, could you please tell me, what are the steps you are following to install gwydion-dylan?, which are the exact libraries that are missing? , and how exactly did you find out this behaviour? (compiling X file, testing X library .. etc) Thanks,
I can't reproduce bug, and i need more info. Closing bug.
Hi. This bug just bit me too. If I am reading the ebuild correctly, the build dependency is either the gwydion-dylan-bin package, or the source package itself. Unfortunately I was not aware of this bug when I first installed, and so did not pay close attention, and did not notice if the ebuild actually _did_ pull in dev-lang/gwydion-dylan-bin. A quick look into /opt, and into my $PKGDIR reveals the absence of "/opt/gwydion-dylan" and "gwydion-dylan-bin-2.4.0-x86.tbz2" so I think we can conclude it did not, as long as the source ebuild does not also automatically uninstall the bin package. As for what libs are missing, I am also new to dylan so I have no frame of reference to answer that, however, I will attach the output of `equery files gwydion-dylan` and you should be able to compare against your own install to deduce this. I can confirm that like Dustin mentioned, "make-dylan-app" is _not_ present. I do however, have its manpage! What I can do is show the result of trying to compile the trivial 'hello world' example from the Gwydion Dylan homepage docs: -------------------- Entering single file mode. Compiling library hello [Loading library Dylan...] [Loading library common-dylan...In Define Library hello.: unknown source locationError: Puked loading library common-dylan: Can't open object dump file "common-dylan.lib.du" ] "<anonymous source buffer>", line 0, characters 26 through 37: define library hello use common-dylan; use io; end; define module hello use common-dylan; use format-out; end; ^^^^^^^^^^^^ Error: Using broken library common-dylan [Loading library io...unknown source locationError: Puked loading library io: Can't open object dump file "io.lib.du" ] "<anonymous source buffer>", line 0, characters 44 through 45: define library hello use common-dylan; use io; end; define module hello use common-dylan; use format-out; end; ^^ Error: Using broken library io In Define Module hello.: "<anonymous source buffer>", line 0, characters 78 through 89: define library hello use common-dylan; use io; end; define module hello use common-dylan; use format-out; end; ^^^^^^^^^^^^ Error: No such module common-dylan in library hello. "<anonymous source buffer>", line 0, characters 96 through 105: define library hello use common-dylan; use io; end; define module hello use common-dylan; use format-out; end; ^^^^^^^^^^ Error: No such module format-out in library hello. Parsing hello.dylan seeding representations Finalizing definitions inheriting slots inheriting overrides laying out instances Optimize called 0 times. Compilation failed with 0 Warnings and 6 Errors ------------------- So: it would seem that "common-dylan" is one of the missing libs. Luis: I am going to re-emerge this as that seems to be the workaround and I want to get this working. However, if there is more info you need just ask, and I can also see if I can reproduce this on another one of my machines if you would like. Let me know, Thanks [1] http://www.opendylan.org/gdref/gduser.html#gduser-simple-hello-world
Created attachment 118767 [details] Output of `equery files gwydion-dylan` after intitial `emerge gwydion-dylan`
