ERROR: In procedure dynamic-link:

ERROR: In procedure dynamic-link:

[Bo Forslund]

Hello!

Guile-gtk used to work but after I installed Mandrake 8.1 i get this
error messages if I try to use it.

ERROR: In procedure dynamic-link:
ERROR: file not found

Whats wrong?

guile is guile-1.4-14mdk

Thanks
Bo

Re: ERROR: In procedure dynamic-link:

[Alexey Rodriguez Y]

On Wednesday 14 November 2001 23:25, Bo Forslund wrote:
> Hello!
>
> Guile-gtk used to work but after I installed Mandrake 8.1 i get this
> error messages if I try to use it.
>
> ERROR: In procedure dynamic-link:
> ERROR: file not found
>
> Whats wrong?
>
> guile is guile-1.4-14mdk
>
> Thanks
> Bo

  Hi Bo, i had the same error in Mandrake 8.1, in Mandrake 8.0 everything was 
fine. I sent an email about this to lists guile-gtk@sourceware.cygnus.com and 
guile-gtk@sources.redhat.com. But both lists seem dead.
  Do this as a temporary workaround. Gtk and gnome libs look for libraries 
without the .so prefix so you must create this symbolic links inside 
/usr/lib:

  ln -s libglade.so libglade
  ln -s libguileglade.so libguileglade
  ln -s libguilegnome.so libguilegnome
  ln -s libguilegtk-1.2.so libguilegtk-1.2

  You may need to run strace to know if you need to symlink more libraries. 
Maybe a better fix would be to edit the scheme file that loads the libs.

  Good luck,

  Alexey

P.S. Are you having any problem with gnome-guile loading glade files?

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

Alexey Rodriguez Y wrote:

>
>   You may need to run strace to know if you need to symlink more libraries.
> Maybe a better fix would be to edit the scheme file that loads the libs.
>

I guess this must be the best. The problem is to know which file to edit =)


Bo Forslund

Re: ERROR: In procedure dynamic-link:

[Alexey Rodriguez Y]

On Thursday 15 November 2001 10:13, Bo Forslund wrote:
> Alexey Rodriguez Y wrote:
> >   You may need to run strace to know if you need to symlink more
> > libraries. Maybe a better fix would be to edit the scheme file that loads
> > the libs.
>
> I guess this must be the best. The problem is to know which file to edit =)
>
>
> Bo Forslund

  I assume you are running guile-gtk directly. guile with use-module is more 
verbose:

$ guile
guile> (use-modules (gtk gtk))
/usr/share/guile/gtk/dynlink.scm:19:34: In procedure dynamic-link in 
expression (dynamic-link libname):
/usr/share/guile/gtk/dynlink.scm:19:34: file not found
ABORT: (misc-error)

the (backtrace) will show you more stuff. I hope you can get the elegant fix 
:). It would be interesting to diff with the version that came with mdk8.
  Btw Bo, i had problems loading .glade files using gnome-guile libglade. I 
cannot exactly repeat the bugs but maybe you have already experienced those.

  Alexey

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

Hello!

How is it with libnames? I have always assumed that the dynamic libs were called
something like libname.so.1.2.3.
Then when running ldconfig, a symbolic link is made called libname.so pointing
at it. I checked /lib and /usr/lib and couldn't see any libname without
extension. Everyone had extensions .a .al .o or .so.

So I did this in dynlink.scm

(define string-append
  (lambda args
    (let f ((ls args) (n 0))
      (if (null? ls)
          (make-string n)
          (let* ((s1 (car ls))
                 (m (string-length s1))
                 (s2 (f (cdr ls) (+ n m))))
            (do ((i 0 (+ i 1)) (j n (+ j 1)))
                ((= i m) s2)
                (string-set! s2 j (string-ref s1 i))))))))

Then at what used to be /usr/share/guile/gtk/dynlink.scm:19:34:
(dynamic-call init-func (dynamic-link (string-append libname ".so")))


Not very elegant but it works.

Shouldn't guile-gtk (or any prog for that matter) always look for libname.so?

I shall find out who is calling dynlinl.scm and have it call for libname.so. Can
You figure out one reason why it not should look for .so?



> :It would be interesting to diff with the version that came with mdk8.

I use the same version of guile-gtk as I did before the mdk upgrade
(guile-gtk-0.19-1) built from the src.rpm. It used to work with Mandrake 7.2 and
( i think ) 8.0.

>
>   Btw Bo, i had problems loading .glade files using gnome-guile libglade. I
> cannot exactly repeat the bugs but maybe you have already experienced those.
>

The only .glade files I know about is the project.glade files to use with the
Glade GUI builder, and they load.

Bo

Re: ERROR: In procedure dynamic-link:

[Marius Vollmer]

Bo Forslund <bo.forslund@abc.se> writes:

> How is it with libnames?

The function `dynamic-link' is supposed to supply the extension on its
own.  This is the reason you shouldn't specify any.  For example,
Guile will first look for a `libtool archive#' with extension ".la".
Such an archive is a short description file that will then direct the
actual loading of the real shared library.  This might be necessary on
platforms that don't support inter-library dependencies, or have funny
versioning schemes.  Also, not all platforms use ".so".  HP/UX uses
".sl" I think, and Win32 uses ".dll".  So it's better the let Guile
choose the extension.

This does not seem to work for you, however.  What version of Guile
are you using?  Maybe we need to make sure that it includes the right
version of libltdl (the lower level that handles all the dirty bits
about dynamic linking).

Libltdl has been known for producing "file not found" error messages
for just about any kind of error.  You can't, unfortunately, assume
that the real cause is indeed some file not being found.

This should have been fixed already, however, but it could be that the
version of Guile that you are using has not yet picked up that fix.

It might be helpful to use `strace' to find out what files guile or
guile-gtk are really looking for and which are opened successfully.

> So I did this in dynlink.scm
> 
> (define string-append

( Why do you define string-append?  There is a builtin string-append. )

> Then at what used to be /usr/share/guile/gtk/dynlink.scm:19:34:
> (dynamic-call init-func (dynamic-link (string-append libname ".so")))
> 
> Not very elegant but it works.

Which is kinda strange.

It _could_ be that you have a very old version of Guile that doesn't
provide its own extensions lib shared libraries.  That would have to
be Guile 1.3.4 or something.

Re: ERROR: In procedure dynamic-link:

[Alexey Rodriguez Y]

  The version of guile in mdk8.1 is 1.4. I found this in /usr/lib

  /usr/lib/libltdl.so.3

  is this a recent version?

  When i straced guile when loading gtk it was looking for some .la files but 
finally it looked for libfoo (without .so). I don't have access to the 
machine right now, i can't provide the strace file.

On Thursday 15 November 2001 19:39, Marius Vollmer wrote:
> Bo Forslund <bo.forslund@abc.se> writes:
> > How is it with libnames?
>
> The function `dynamic-link' is supposed to supply the extension on its
> own.  This is the reason you shouldn't specify any.  For example,
> Guile will first look for a `libtool archive#' with extension ".la".
> Such an archive is a short description file that will then direct the
> actual loading of the real shared library.  This might be necessary on
> platforms that don't support inter-library dependencies, or have funny
> versioning schemes.  Also, not all platforms use ".so".  HP/UX uses
> ".sl" I think, and Win32 uses ".dll".  So it's better the let Guile
> choose the extension.
>
> This does not seem to work for you, however.  What version of Guile
> are you using?  Maybe we need to make sure that it includes the right
> version of libltdl (the lower level that handles all the dirty bits
> about dynamic linking).
>
> Libltdl has been known for producing "file not found" error messages
> for just about any kind of error.  You can't, unfortunately, assume
> that the real cause is indeed some file not being found.
>
> This should have been fixed already, however, but it could be that the
> version of Guile that you are using has not yet picked up that fix.
>
> It might be helpful to use `strace' to find out what files guile or
> guile-gtk are really looking for and which are opened successfully.
>
> > So I did this in dynlink.scm
> >
> > (define string-append
>
> ( Why do you define string-append?  There is a builtin string-append. )
>
> > Then at what used to be /usr/share/guile/gtk/dynlink.scm:19:34:
> > (dynamic-call init-func (dynamic-link (string-append libname ".so")))
> >
> > Not very elegant but it works.
>
> Which is kinda strange.
>
> It _could_ be that you have a very old version of Guile that doesn't
> provide its own extensions lib shared libraries.  That would have to
> be Guile 1.3.4 or something.

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

Hi!

It seems like dynlink.scm get the libname from ../gtk-1.2/gdk.scm and
../gtk-1.2/gtk.scm. Then there is a dynlink-old.scm that is looking for
different libname extensions but it doesnt seem to be used.

It seems to me that the only lib dynlink.scm is looking for is libguilegtk-1.2.
Is it a bad idea to make some mechanism that decide what OS is running it and
pass the correct libname to /usr/share/guile/gtk-1.2/gdk.scm and
/usr/share/guile/gtk-1.2/gtk.scm?

This line in gtk.scm and gdk.scm
(merge-compiled-code "sgtk_init_gtk_gdk_glue" "libguilegtk-1.2.so")

and commenting out :use-module(gtk dynlink-old) works for me.

(define-module (gtk dynlink)
  :use-module (gtk config)
  ;;  :use-module (gtk dynlink-old)
  )

Would it be possible to put in an appropriate libname extension during make, in
for example config.scm.

Bo

Re: ERROR: In procedure dynamic-link:

[Marius Vollmer]

Bo Forslund <bo.forslund@abc.se> writes:

> Is it a bad idea to make some mechanism that decide what OS is
> running it and pass the correct libname to
> /usr/share/guile/gtk-1.2/gdk.scm and
> /usr/share/guile/gtk-1.2/gtk.scm?

Yes.  The OS specifica should be taken care of by `dynamic-link'
itself, via libltdl.  That's why you shouldn't specify a file name
extension to dynamic-link, it will provide the correct one on its own.

The setup in guile-gtk should work as it is.  When it doesn't work, we
need to find the reason.  Shared libraries are somewhat wicked, and so
the reason can be quite subtle.

More on this later...

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

I think it is guile that is failing. I tried guile-1.5.4 and it loads the
libs with libname without ".so". I tested it with the hello-world.scm
example. guile-gtk doesn't compile with guile-1.5.4 so I tested with
guile-gtk compiled with the guile-1.4 headers. It brings up the gtk GUI
with error messages about "some deprecated features have been used".



guile-gtk 0.19 doesn't compile with guie-1.5.4. It gives this messages


[bo@li guile-gtk-0.19]$ make
guile-snarf -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include -I/usr/include
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/X11R6/include  -g -O2 guile-gtk.c >guile-gtk.c.tmp && mv
guile-gtk.c.tmp guile-gtk.x
guile-snarf -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include -I/usr/include
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/X11R6/include  -g -O2 gtk-support.c >gtk-support.c.tmp && mv
gtk-support.c.tmp gtk-support.x
gtk-support.c:622:25: gtk-support.x: No such file or directory
make: *** [gtk-support.x] Error 1
make: *** Waiting for unfinished jobs....
guile-gtk.c:2715:23: guile-gtk.x: No such file or directory
make: *** [guile-gtk.x] Error 1



So until guile handle dynamic linking as it is supposed one have to
either so "ln -s libguilegtk-1.2.so libguilegtk-1.2" or explicitly tell
guile-gtk to look for libguilegtk-1.2.so.

Any ideas how to get guile-gtk to compile with guile-1.5.4?

Regards
Bo

Re: ERROR: In procedure dynamic-link:

[Marius Vollmer]

Bo Forslund <bo.forslund@abc.se> writes:

> I think it is guile that is failing. I tried guile-1.5.4 and it loads the
> libs with libname without ".so". I tested it with the hello-world.scm
> example. guile-gtk doesn't compile with guile-1.5.4 so I tested with
> guile-gtk compiled with the guile-1.4 headers. It brings up the gtk GUI
> with error messages about "some deprecated features have been used".

This is OK.

> guile-gtk 0.19 doesn't compile with guie-1.5.4. It gives this messages
>
> [...] 
> gtk-support.c:622:25: gtk-support.x: No such file or directory

The error must have happened further up, probably during the
generation of gtk-support.x.

> Any ideas how to get guile-gtk to compile with guile-1.5.4?

Use guile-gtk from CVS.

Re: ERROR: In procedure dynamic-link:

[Marius Vollmer]

Alexey Rodriguez Y <alexey@memi.umss.edu.bo> writes:

>   The version of guile in mdk8.1 is 1.4. I found this in /usr/lib
> 
>   /usr/lib/libltdl.so.3
> 
>   is this a recent version?

Guile has libltdl compiled in normally, I don't know what Mandrake
does.  You can check with "ldd" whether Guile is using
/usr/lib/libltdl.so.

> When i straced guile when loading gtk it was looking for some .la
> files but finally it looked for libfoo (without .so). I don't have
> access to the machine right now, i can't provide the strace file.

It would be important to see the actual strace output to find out what
is happening.

Re: ERROR: In procedure dynamic-link:

[Alexey Rodriguez Y]

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

  I am sending the output of strace when i run guile-gtk. Sorry i did not cut 
to the relevant parts, i though maybe you wanted to see all of it.

  The ldd doesn't show libltdl maybe it is statically linked i don't know i 
can get the src.rpm and check it.

  The output is like this:

	libguilegtk-1.2.so.0 => /usr/lib/libguilegtk-1.2.so.0 (0x4002b000)
	libm.so.6 => /lib/libm.so.6 (0x40083000)
	libguile.so.9 => /usr/lib/libguile.so.9 (0x400a6000)
	libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x4012f000)
	libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x40278000)
	libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x402b2000)
	libgthread-1.2.so.0 => /usr/lib/libgthread-1.2.so.0 (0x402b5000)
	libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x402b8000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x402de000)
	libdl.so.2 => /lib/libdl.so.2 (0x402f5000)
	libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x402f9000)
	libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40301000)
	libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40311000)
	libc.so.6 => /lib/libc.so.6 (0x403fb000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

  Thanks for your help.

  Alexey

On Monday 19 November 2001 18:42, Marius Vollmer wrote:
> Alexey Rodriguez Y <alexey@memi.umss.edu.bo> writes:
> >   The version of guile in mdk8.1 is 1.4. I found this in /usr/lib
> >
> >   /usr/lib/libltdl.so.3
> >
> >   is this a recent version?
>
> Guile has libltdl compiled in normally, I don't know what Mandrake
> does.  You can check with "ldd" whether Guile is using
> /usr/lib/libltdl.so.
>
> > When i straced guile when loading gtk it was looking for some .la
> > files but finally it looked for libfoo (without .so). I don't have
> > access to the machine right now, i can't provide the strace file.
>
> It would be important to see the actual strace output to find out what
> is happening.

[-- Attachment #2: guile-gtk.strace.gz --]
[-- Type: application/x-gzip, Size: 9382 bytes --]

Re: ERROR: In procedure dynamic-link:

[Marius Vollmer]

Alexey Rodriguez Y <alexey@memi.umss.edu.bo> writes:

>   I am sending the output of strace when i run guile-gtk.

Ahh, so you are running guile-gtk, as opposed to just guile.  Sorry, I
didn't noticed that earlier.

With guile-gtk, no dynamic loading of libguilegtk-1.2 should happen.
That is (was) the point of guile-gtk: it should work on systems where
dynamic linking would not.

From your strace output:

    open("i686/mmx/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    open("i686/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    open("mmx/libguilegtk-1.2.so.0", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    open("libguilegtk-1.2.so.0", O_RDONLY)  = -1 ENOENT
         (No such file or directory)
    open("/etc/ld.so.cache", O_RDONLY)      = 3
    fstat64(3, {st_mode=S_IFREG|0644, st_size=78514, ...}) = 0
    old_mmap(NULL, 78514, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40017000
    close(3)                                = 0
    open("/usr/lib/libguilegtk-1.2.so.0", O_RDONLY) = 3

This shows what the OS is doing when starting guile-gtk, "main" has
not yet been called.  You can see that is checks various locations
(probably from your LD_LIBRARY_PATH, right?) and then goes on to consult
/etc/ld.so.cache to find libguilegtk-1.2.so.0 in /usr/lib.

Later:

    open("/users/alexey/proyecto/cint/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    open("i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    open("i686/libguilegtk-1.2", O_RDONLY)  = -1 ENOENT
         (No such file or directory)
    open("mmx/libguilegtk-1.2", O_RDONLY)   = -1 ENOENT
         (No such file or directory)
    open("libguilegtk-1.2", O_RDONLY)       = -1 ENOENT
         (No such file or directory)
    open("/etc/ld.so.cache", O_RDONLY)      = 5
    fstat64(5, {st_mode=S_IFREG|0644, st_size=78514, ...}) = 0
    old_mmap(NULL, 78514, PROT_READ, MAP_PRIVATE, 5, 0) = 0x406ae000
    close(5)                                = 0
    open("/lib/i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/lib/i686/mmx", 0xbfffe640)     = -1 ENOENT
         (No such file or directory)
    open("/lib/i686/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/lib/i686", 0xbfffe640)         = -1 ENOENT
         (No such file or directory)
    open("/lib/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/lib/mmx", 0xbfffe640)          = -1 ENOENT
         (No such file or directory)
    open("/lib/libguilegtk-1.2", O_RDONLY)  = -1 ENOENT
         (No such file or directory)
    stat64("/lib", {st_mode=S_IFDIR|0755, st_size=4864, ...}) = 0
    open("/usr/lib/i686/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/usr/lib/i686/mmx", 0xbfffe640) = -1 ENOENT
         (No such file or directory)
    open("/usr/lib/i686/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/usr/lib/i686", 0xbfffe640)     = -1 ENOENT
         (No such file or directory)
    open("/usr/lib/mmx/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/usr/lib/mmx", 0xbfffe640)      = -1 ENOENT
         (No such file or directory)
    open("/usr/lib/libguilegtk-1.2", O_RDONLY) = -1 ENOENT
         (No such file or directory)
    stat64("/usr/lib", {st_mode=S_IFDIR|0755, st_size=62712, ...}) = 0
    munmap(0x406ae000, 78514)               = 0
    open("libguilegtk-1.2.la", O_RDONLY)    = -1 ENOENT
         (No such file or directory)
    write(2, "ERROR", 5)                    = 5
    write(2, ": ", 2)                       = 2
    write(2, "In procedure ", 13)           = 13
    write(2, "dynamic-link", 12)            = 12
    write(2, ":\n", 2)                      = 2
    write(2, "ERROR", 5)                    = 5
    write(2, ": ", 2)                       = 2
    write(2, "file not found", 14)          = 14
    write(2, "\n", 1)                       = 1

This looks very strange indeed, and does not fit with what I would
expect from the dynamic linking code in guile-1.4.  The log above does
show no searching for a ".la" file, and no attempt at an ".so" file at
all.

I'm confused now.  I think it would be best if you remove the Mandrake
guile packages from your system and install guile-1.5 from source.  Bo
Forslund can help you with that, I think.

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

Marius Vollmer wrote:

>
> I'm confused now.  I think it would be best if you remove the Mandrake
> guile packages from your system and install guile-1.5 from source.  Bo
> Forslund can help you with that, I think.

I think I can.  I suspect that it is guile 1-4 itself that is failing ( not sure
though ) so I tested with guile-1.5.4. Guil-1.5.4 requres the new version of
guile-gtk I got from Marius Vollmer.

I have made rpm packages of guile-1.5.4 and guile-gtk-20011121. The safest is to
take the source rpms and rebuild. I think I upgraded gtk+ and gdk.

ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm

The guile package is split into a guile,  libguile, libguile-devel and a
guile-srfi package. Perhaps oop and scripts should be in its own packages?
Please tell someone.

In case You don't know. Put the files in /usr/src/RPM/SRPMS and then
    rpm --rebuild guile-1.5.4-3mdk.src.rpm
    rpm --rebuild guile-gtk-20011121-1.src.rpm

The compiled packages will appear in /usr/src/RPM/RPMS/i686/.

(or even better and safer, set up your user account so you can build rpms)

Regards
Bo

guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Steve Tell]

On Sun, 25 Nov 2001, Bo Forslund wrote:

> I think I can.  I suspect that it is guile 1-4 itself that is failing ( not sure
> though ) so I tested with guile-1.5.4. Guil-1.5.4 requres the new version of
> guile-gtk I got from Marius Vollmer.
> 
> I have made rpm packages of guile-1.5.4 and guile-gtk-20011121. The safest is to
> take the source rpms and rebuild. I think I upgraded gtk+ and gdk.
> 
> ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
> ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm

It seems that geek.mine.nu is not accepting anonymous FTP - are these
available anywhere else?

Actually, what I'm really looking for is simply a guile-gtk snapshot
tarball that has already had all of the gnome-pkgconfig nonsense run and
is ready to configure.  Despite looking though several old messages, I've
been unable to figure out how to get pkgconfig-0.8.0 and CVS gnome-common
to enable me to autogen and configure CVS guile-gtk.

I'm hoping to build a guile-gtk that works with guile-1.5.4 in a seperate
$prefix so I can then test-build an application.  Is this going to be
possible without removing guile-1.4 and guile-gtk-0.19 from /usr or
constructing a complete chroot'ed universe?

Steve

 
--
Steve Tell  tell@telltronics.org 

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Steve Tell]

On Thu, 27 Dec 2001, Steve Tell wrote:

> Actually, what I'm really looking for is simply a guile-gtk snapshot
> tarball that has already had all of the gnome-pkgconfig nonsense run and
> is ready to configure.  Despite looking though several old messages, I've
> been unable to figure out how to get pkgconfig-0.8.0 and CVS gnome-common
> to enable me to autogen and configure CVS guile-gtk.

To followup my own question, it seems that CVS guile-gtk as of last night
doesn't really need gnome-common and pkgconfig; running the traditional 
autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
enables it to configure and build.

Now off to debug the compilation of my application...

--
Steve Tell  tell@telltronics.org 

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

Steve Tell wrote:

> On Thu, 27 Dec 2001, Steve Tell wrote:
> To followup my own question, it seems that CVS guile-gtk as of last night
> doesn't really need gnome-common and pkgconfig; running the traditional
> autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
> enables it to configure and build.
>

This is what I do in the  rpm package. ( or at least what I intended to heh... )
I did it live in the BUILD dir and everything worked nice.  But I couldn't get
the rpm working until I realized that forgot to add the lines to the spec file.
The testing tree of guile-gtk worked but the rpm version did not. It was a bit
tricky to keep track of which version was running.

I almost believed in ghosts for a while. =)

here is a source rpm
/home/bo/tmp/guile-gtk-20011121-7.src.rpm

The patch used in the rpm comes as an attach.
guile-gtk-20011121/Makefile.am  and  guile-gtk-20011121/examples/configure.in are
changed.

Bo

[-- Attachment #2: guile-gtk-20011121-5.patch --]
[-- Type: text/plain, Size: 2745 bytes --]

diff -Nur guile-gtk-20011121-virgin/Makefile.am guile-gtk-20011121/Makefile.am
--- guile-gtk-20011121-virgin/Makefile.am	Tue Nov 13 00:06:08 2001
+++ guile-gtk-20011121/Makefile.am	Fri Dec 28 22:39:15 2001
@@ -1,26 +1,20 @@
 # -*- Makefile -*-
 
-autoconf_macros = gnome-guile-checks.m4
-acinclude.m4: $(autoconf_macros)
-	cd $(srcdir); \
-	cat $(autoconf_macros) > acim.tmp; \
-	mv acim.tmp acinclude.m4
-
-#bin_PROGRAMS    = $(GUILE_GTK_VERSION)
+bin_PROGRAMS    = $(GUILE_GTK_VERSION)
 bin_SCRIPTS     = build-guile-gtk
 lib_LTLIBRARIES = $(LIBGUILEGTK_VERSION) $(LIBGUILEDLOPENHELPER)
 
-#EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
+EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
 EXTRA_LTLIBRARIES = libguilegtk-1.2.la libguilegtk-1.3.la \
                     libguiledlopenhelper.la
 
-#guile_gtk_1_2_SOURCES = main.c
-#guile_gtk_1_2_LDFLAGS = -export-dynamic
-#guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
-
-#guile_gtk_1_3_SOURCES = main.c
-#guile_gtk_1_3_LDFLAGS = -export-dynamic
-#guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
+guile_gtk_1_2_SOURCES = main.c
+guile_gtk_1_2_LDFLAGS = -export-dynamic
+guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
+
+guile_gtk_1_3_SOURCES = main.c
+guile_gtk_1_3_LDFLAGS = -export-dynamic
+guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
 
 INCLUDES = $(GTK_CFLAGS) -I$(includedir) $(GUILE_INCS)
 
@@ -68,9 +62,9 @@
 
 include_HEADERS = guile-gtk.h
 
-#install-exec-local:
-#	mkdir -p $(bindir)
-#	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
+install-exec-local:
+	mkdir -p $(bindir)
+	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
 
 gtkmoduledir = $(datadir)/guile/gtk
 vgtkmoduledir = $(datadir)/guile/gtk-$(GTK_VERSION)
@@ -109,8 +103,8 @@
 gdk-glue.c: $(gdkdefs) build-guile-gtk
 	$(BUILD) -I $(srcdir) glue $(gdkdefs) >tmpd && mv tmpd $@
 
-#main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
-#	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
+main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
+	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
 
 Makefile: $(BUILT_SOURCES)
 
diff -Nur guile-gtk-20011121-virgin/examples/configure.in guile-gtk-20011121/examples/configure.in
--- guile-gtk-20011121-virgin/examples/configure.in	Sat Dec  2 13:10:27 2000
+++ guile-gtk-20011121/examples/configure.in	Fri Dec 28 22:42:41 2001
@@ -5,14 +5,6 @@
 AC_PROG_CC
 AM_PROG_LIBTOOL
 
-GNOME_COMMON_INIT
-GNOME_PLATFORM_GNOME_2(no)
-
-if test $platform_gnome_2 = yes ; then
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+-2.0:1.3.1)
-else
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+:1.2.6)
-fi
 AC_SUBST(GTK_CFLAGS)
 AC_SUBST(GTK_LIBS)
 

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

Bo Forslund wrote:

> here is a source rpm
> /home/bo/tmp/guile-gtk-20011121-7.src.rpm
>

Hrrrmmm.... rather

ftp://geek.mine.nu/pub/RPMS/guile-gtk-20011121-7.i686.rpm

pasted from the wrong text entry heh...

Bo

Yet a new version (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

I think I found what's wrong. It is not the package as a whole.

I used the exapmles to check whether the rpm builds were OK. I thought
that if the examples compiled OK then the package would be OK. I
suspected that it might be a SMP problem, and it might be. But not when
it comes to compile the package, only when it comes to compile the
examples. I think that the pagkage was built OK every time. It was just
the examples that were failing

I think it is last few lines in Makefile.am that is failing

foo-glue.c: foo.defs
        build-guile-gtk glue $< >tmp && mv tmp $@

main.c: foo.defs
        build-guile-gtk main $< >tmp && mv tmp $@

With this above in Makefile.am a build would fail 9 times of 10 or so.

I dont really understand how this works but I think the tmp-something is
deleted before the final file is ready written and that it is here it
might be an SMP problem. I am building on a dual CPU box.



Whith this  in Automake.am it works. I have tried several builds.

foo-glue.c: foo.defs
        build-guile-gtk glue $< >$@

main.c: foo.defs
        build-guile-gtk main $< >$@


Here is the last src.rpm
ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-8.src.rpm

The latest patch comes as an attach

G'nite
Bo


[-- Attachment #2: guile-gtk-20011121-8.patch --]
[-- Type: text/plain, Size: 3291 bytes --]

diff -Nur guile-gtk-20011121-virgin/Makefile.am guile-gtk-20011121/Makefile.am
--- guile-gtk-20011121-virgin/Makefile.am	Tue Nov 13 00:06:08 2001
+++ guile-gtk-20011121/Makefile.am	Sat Dec 29 03:45:51 2001
@@ -1,26 +1,20 @@
 # -*- Makefile -*-
 
-autoconf_macros = gnome-guile-checks.m4
-acinclude.m4: $(autoconf_macros)
-	cd $(srcdir); \
-	cat $(autoconf_macros) > acim.tmp; \
-	mv acim.tmp acinclude.m4
-
-#bin_PROGRAMS    = $(GUILE_GTK_VERSION)
+bin_PROGRAMS    = $(GUILE_GTK_VERSION)
 bin_SCRIPTS     = build-guile-gtk
 lib_LTLIBRARIES = $(LIBGUILEGTK_VERSION) $(LIBGUILEDLOPENHELPER)
 
-#EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
+EXTRA_PROGRAMS = guile-gtk-1.2 guile-gtk-1.3
 EXTRA_LTLIBRARIES = libguilegtk-1.2.la libguilegtk-1.3.la \
                     libguiledlopenhelper.la
 
-#guile_gtk_1_2_SOURCES = main.c
-#guile_gtk_1_2_LDFLAGS = -export-dynamic
-#guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
-
-#guile_gtk_1_3_SOURCES = main.c
-#guile_gtk_1_3_LDFLAGS = -export-dynamic
-#guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
+guile_gtk_1_2_SOURCES = main.c
+guile_gtk_1_2_LDFLAGS = -export-dynamic
+guile_gtk_1_2_LDADD = libguilegtk-1.2.la $(GUILE_LIBS) $(GTK_LIBS)
+
+guile_gtk_1_3_SOURCES = main.c
+guile_gtk_1_3_LDFLAGS = -export-dynamic
+guile_gtk_1_3_LDADD = libguilegtk-1.3.la $(GUILE_LIBS) $(GTK_LIBS)
 
 INCLUDES = $(GTK_CFLAGS) -I$(includedir) $(GUILE_INCS)
 
@@ -68,9 +62,9 @@
 
 include_HEADERS = guile-gtk.h
 
-#install-exec-local:
-#	mkdir -p $(bindir)
-#	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
+install-exec-local:
+	mkdir -p $(bindir)
+	cd $(bindir) && rm -f guile-gtk && $(LN_S) $(GUILE_GTK_VERSION) guile-gtk
 
 gtkmoduledir = $(datadir)/guile/gtk
 vgtkmoduledir = $(datadir)/guile/gtk-$(GTK_VERSION)
@@ -109,8 +103,8 @@
 gdk-glue.c: $(gdkdefs) build-guile-gtk
 	$(BUILD) -I $(srcdir) glue $(gdkdefs) >tmpd && mv tmpd $@
 
-#main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
-#	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
+main.c:  $(gtkdefs) $(gdkdefs) build-guile-gtk
+	$(BUILD) -I $(srcdir) main $(gtkdefs) $(gdkdefs) >tmpm && mv tmpm $@
 
 Makefile: $(BUILT_SOURCES)
 
diff -Nur guile-gtk-20011121-virgin/examples/Makefile.am guile-gtk-20011121/examples/Makefile.am
--- guile-gtk-20011121-virgin/examples/Makefile.am	Sun Apr 16 22:19:46 2000
+++ guile-gtk-20011121/examples/Makefile.am	Sat Dec 29 03:49:11 2001
@@ -16,10 +16,10 @@
 BUILT_SOURCES = foo-glue.c main.c
 
 foo-glue.c: foo.defs
-	build-guile-gtk glue $< >tmp && mv tmp $@
+	build-guile-gtk glue $< >$@
 
 main.c: foo.defs
-	build-guile-gtk main $< >tmp && mv tmp $@
+	build-guile-gtk main $< >$@
 
 scmgtkdir=$(datadir)/guile/gtk
 scmgtk_DATA = foo.scm
diff -Nur guile-gtk-20011121-virgin/examples/configure.in guile-gtk-20011121/examples/configure.in
--- guile-gtk-20011121-virgin/examples/configure.in	Sat Dec  2 13:10:27 2000
+++ guile-gtk-20011121/examples/configure.in	Sat Dec 29 03:45:51 2001
@@ -5,14 +5,6 @@
 AC_PROG_CC
 AM_PROG_LIBTOOL
 
-GNOME_COMMON_INIT
-GNOME_PLATFORM_GNOME_2(no)
-
-if test $platform_gnome_2 = yes ; then
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+-2.0:1.3.1)
-else
-  GNOME_PKGCONFIG_CHECK_MODULES(GTK, gtk+:1.2.6)
-fi
 AC_SUBST(GTK_CFLAGS)
 AC_SUBST(GTK_LIBS)
 

Yet a new version (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

I think I found what's wrong. It is not the package as a whole.

I used the exapmles to check whether the rpm builds were OK. I thought
that if the examples compiled OK then the package would be OK. I
suspected that it might be a SMP problem, and it might be. But not when
it comes to compile the package, only when it comes to compile the
examples. I think that the pagkage was built OK every time. It was just
the examples that were failing

I think it is last few lines in Makefile.am that is failing

foo-glue.c: foo.defs
        build-guile-gtk glue $< >tmp && mv tmp $@

main.c: foo.defs
        build-guile-gtk main $< >tmp && mv tmp $@

With this above in Makefile.am a build would fail 9 times of 10 or so.

I dont really understand how this works but I think the tmp-something is
deleted before the final file is ready written and that it is here it
might be an SMP problem. I am building on a dual CPU box.



Whith this  in Automake.am it works. I have tried several builds.

foo-glue.c: foo.defs
        build-guile-gtk glue $< >$@

main.c: foo.defs
        build-guile-gtk main $< >$@


Here is the last src.rpm
ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-8.src.rpm

The latest patch comes as an attach

G'nite
Bo

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

Bo Forslund wrote:

> here is a source rpm
> /home/bo/tmp/guile-gtk-20011121-7.src.rpm
>

Hrrrmmm.... rather

ftp://geek.mine.nu/pub/RPMS/guile-gtk-20011121-7.i686.rpm

pasted from the wrong text entry heh...

Bo

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Bo Forslund]

Steve Tell wrote:

> On Thu, 27 Dec 2001, Steve Tell wrote:
> To followup my own question, it seems that CVS guile-gtk as of last night
> doesn't really need gnome-common and pkgconfig; running the traditional
> autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
> enables it to configure and build.
>

This is what I do in the  rpm package. ( or at least what I intended to heh... )
I did it live in the BUILD dir and everything worked nice.  But I couldn't get
the rpm working until I realized that forgot to add the lines to the spec file.
The testing tree of guile-gtk worked but the rpm version did not. It was a bit
tricky to keep track of which version was running.

I almost believed in ghosts for a while. =)

here is a source rpm
/home/bo/tmp/guile-gtk-20011121-7.src.rpm

The patch used in the rpm comes as an attach.
guile-gtk-20011121/Makefile.am  and  guile-gtk-20011121/examples/configure.in are
changed.

Bo

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Steve Tell]

On Thu, 27 Dec 2001, Steve Tell wrote:

> Actually, what I'm really looking for is simply a guile-gtk snapshot
> tarball that has already had all of the gnome-pkgconfig nonsense run and
> is ready to configure.  Despite looking though several old messages, I've
> been unable to figure out how to get pkgconfig-0.8.0 and CVS gnome-common
> to enable me to autogen and configure CVS guile-gtk.

To followup my own question, it seems that CVS guile-gtk as of last night
doesn't really need gnome-common and pkgconfig; running the traditional 
autogen procedure, "aclocal; automake --add-missing-gnu; autoheader; autoconf"
enables it to configure and build.

Now off to debug the compilation of my application...

--
Steve Tell  tell@telltronics.org 

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Ariel Rios]

On Thu, 2001-12-27 at 23:28, Steve Tell wrote:
 
> > ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
> > ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm
mmm
I can only say I am sorry...

I finished school for good...
I am on holidays...
I was not aware of these messages...

I will be doing a new pre 0.20 tarball sometime next week

ariel

Re: guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Ariel Rios]

On Thu, 2001-12-27 at 23:28, Steve Tell wrote:
 
> > ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
> > ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm
mmm
I can only say I am sorry...

I finished school for good...
I am on holidays...
I was not aware of these messages...

I will be doing a new pre 0.20 tarball sometime next week

ariel

guile-gtk snapshot (was Re: ERROR: In procedure dynamic-link:)

[Steve Tell]

On Sun, 25 Nov 2001, Bo Forslund wrote:

> I think I can.  I suspect that it is guile 1-4 itself that is failing ( not sure
> though ) so I tested with guile-1.5.4. Guil-1.5.4 requres the new version of
> guile-gtk I got from Marius Vollmer.
> 
> I have made rpm packages of guile-1.5.4 and guile-gtk-20011121. The safest is to
> take the source rpms and rebuild. I think I upgraded gtk+ and gdk.
> 
> ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
> ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm

It seems that geek.mine.nu is not accepting anonymous FTP - are these
available anywhere else?

Actually, what I'm really looking for is simply a guile-gtk snapshot
tarball that has already had all of the gnome-pkgconfig nonsense run and
is ready to configure.  Despite looking though several old messages, I've
been unable to figure out how to get pkgconfig-0.8.0 and CVS gnome-common
to enable me to autogen and configure CVS guile-gtk.

I'm hoping to build a guile-gtk that works with guile-1.5.4 in a seperate
$prefix so I can then test-build an application.  Is this going to be
possible without removing guile-1.4 and guile-gtk-0.19 from /usr or
constructing a complete chroot'ed universe?

Steve

 
--
Steve Tell  tell@telltronics.org 

Re: ERROR: In procedure dynamic-link:

[Bo Forslund]

Marius Vollmer wrote:

>
> I'm confused now.  I think it would be best if you remove the Mandrake
> guile packages from your system and install guile-1.5 from source.  Bo
> Forslund can help you with that, I think.

I think I can.  I suspect that it is guile 1-4 itself that is failing ( not sure
though ) so I tested with guile-1.5.4. Guil-1.5.4 requres the new version of
guile-gtk I got from Marius Vollmer.

I have made rpm packages of guile-1.5.4 and guile-gtk-20011121. The safest is to
take the source rpms and rebuild. I think I upgraded gtk+ and gdk.

ftp://geek.mine.nu/pub/SRPMS/guile-1.5.4-2mdk.src.rpm
ftp://geek.mine.nu/pub/SRPMS/guile-gtk-20011121-1.src.rpm

The guile package is split into a guile,  libguile, libguile-devel and a
guile-srfi package. Perhaps oop and scripts should be in its own packages?
Please tell someone.

In case You don't know. Put the files in /usr/src/RPM/SRPMS and then
    rpm --rebuild guile-1.5.4-3mdk.src.rpm
    rpm --rebuild guile-gtk-20011121-1.src.rpm

The compiled packages will appear in /usr/src/RPM/RPMS/i686/.

(or even better and safer, set up your user account so you can build rpms)

Regards
Bo