Pierre | 7 Aug 2006 00:09
Picon

[bug #17344] Problem compiling guile 1.8.0


URL:
  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=17344>

                 Summary: Problem compiling guile 1.8.0
                 Project: Guile
            Submitted by: pierre42
            Submitted on: lundi 07.08.2006 à 00:09
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open

    _______________________________________________________

Details:

# make
make  all-recursive
make[1]: Entering directory `/tmp/guile-1.8.0'
Making all in oop
make[2]: Entering directory `/tmp/guile-1.8.0/oop'
Making all in goops
make[3]: Entering directory `/tmp/guile-1.8.0/oop/goops'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/guile-1.8.0/oop/goops'
make[3]: Entering directory `/tmp/guile-1.8.0/oop'
(Continue reading)

Kevin Ryde | 9 Aug 2006 03:05
Picon
Picon

Re: [bug #17344] Problem compiling guile 1.8.0

Pierre <pierre42d <at> 9online.fr> writes:
>
> gcc -s -O3 -march=i686 -Wall -Wmissing-prototypes -Werror -o .libs/guile
> .libs/guileS.o -pthread guile-guile.o -Wl,--export-dynamic 
> ./.libs/libguile.so /usr/local/lib/libgmp.so -lcrypt -lm
> /usr/local/lib/libltdl.so
> guile-guile.o: In function `main':
> guile.c:(.text+0x2f): undefined reference to
> `lt__PROGRAM__LTX_preloaded_symbols'

What system is this?  You could try delete the following two lines
from libguile/guile.c, they're not needed on a gnu system.

	extern const lt_dlsymlist lt_preloaded_symbols[];
	lt_dlpreload_default (lt_preloaded_symbols);

Dunno why the symbol is "lt__PROGRAM__LTX_preloaded_symbols" though.

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Vivek raghunathan | 10 Aug 2006 17:13
Picon

bug in guile-core/ice-9/slib.scm

All,

As part of a networking project I am working on, I had to port forward
our existing codebase from Guile 1.6 to Guile 1.8. On doing so, I
started getting errors of the form (on running):

ERROR: Unbound variable: with-load-pathname

I dug around a little, and discovered that a thread that discussed
this problem for Guile 1.6-7 with GNUCash. I am new to Guile and don't
understand this really well, but apparently, slib.scm needs to pull in
guile.init to get support for with-load-pathname. Using the same
technique worked for Guile 1.8 for my application.

I don't understand the Guile codebase well enough, and am not sure if
this has already been fixed in current - I think it hasn't. I am
attaching a patch against
guile-core/ice-9/slib.scm v1.46 in your CVS (the branching point for
Guile 1.8).

Vivek

--- slib.scm.1.46   2006-08-10 11:01:32.000000000 -0400
+++ slib.scm    2006-08-10 11:03:26.000000000 -0400
 <at>  <at>  -1,6 +1,6  <at>  <at> 
 ;;;; slib.scm --- definitions needed to get SLIB to work with Guile
 ;;;;
-;;;;   Copyright (C) 1997, 1998, 2000, 2001, 2002, 2003, 2004 Free
Software Foundation, Inc.
+;;;;   Copyright (C) 1997, 1998, 2000, 2001, 2002, 2003, 2004, 2006
(Continue reading)

Vivek raghunathan | 10 Aug 2006 17:08
Picon

bug in guile-core/ice-9/slib.scm

All,

As part of a networking project I am working on, I had to port forward
our existing codebase from Guile 1.6 to Guile 1.8. On doing so, I
started getting errors of the form (on running):

ERROR: Unbound variable: with-load-pathname

I dug around a little, and discovered that a thread that discussed
this problem for Guile 1.6-7 with GNUCash. I am new to Guile and don't
understand this really well, but apparently, slib.scm needs to pull in
guile.init to get support for with-load-pathname. Using the same
technique worked for Guile 1.8 for my application.

I don't understand the Guile codebase well enough, and am not sure if
this has already been fixed. I am attaching a patch against
guile-core/ice-9/slib.scm v1.46 in your CVS (the branching point for
Guile 1.8).

Vivek

--- slib.scm.1.46   2006-08-10 11:01:32.000000000 -0400
+++ slib.scm    2006-08-10 11:03:26.000000000 -0400
 <at>  <at>  -1,6 +1,6  <at>  <at> 
 ;;;; slib.scm --- definitions needed to get SLIB to work with Guile
 ;;;;
-;;;;   Copyright (C) 1997, 1998, 2000, 2001, 2002, 2003, 2004 Free
Software Foundation, Inc.
+;;;;   Copyright (C) 1997, 1998, 2000, 2001, 2002, 2003, 2004, 2006
Free Software Foundation, Inc.
(Continue reading)

Kevin Ryde | 11 Aug 2006 01:16
Picon
Picon

Re: bug in guile-core/ice-9/slib.scm

"Vivek raghunathan" <vivek.raghunathan <at> gmail.com> writes:
>
> I dug around a little, and discovered that a thread that discussed
> this problem for Guile 1.6-7 with GNUCash. I am new to Guile and don't
> understand this really well, but apparently, slib.scm needs to pull in
> guile.init to get support for with-load-pathname. Using the same
> technique worked for Guile 1.8 for my application.

There's a fix in the 1.6 branch that's on its way to the 1.8 branch.

For now the suggestion is to follow the slib manual if you're using
slib, which is "guile -l guile.init".

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Rob Browning | 13 Aug 2006 01:01

Re: bug in guile-core/ice-9/slib.scm

Kevin Ryde <user42 <at> zip.com.au> writes:

> There's a fix in the 1.6 branch that's on its way to the 1.8 branch.
>
> For now the suggestion is to follow the slib manual if you're using
> slib, which is "guile -l guile.init".

Actually, Guile 1.8 just doesn't support SLIB yet, and I'm not sure
how soon it will.  I've been trying to fix that, and have been in a
discussion with the SLIB author about what the fix should look like,
but we haven't finished that discussion yet.

I suspect the slib.scm will look similar to the one in 1.6, but the
upstream guile.init will probably be different, given the changes in
1.8.

--

-- 
Rob Browning
rlb  <at> defaultvalue.org and  <at> debian.org; previously  <at> cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Nils Durner | 22 Aug 2006 18:42
Picon

MinGW port

Hi,

the attached patch fixes compiler errors on Win32/MinGW.

Best,

Nils Durner
diff -Naur guile-core/libguile/posix.c guile-core.nd/libguile/posix.c
--- guile-core/libguile/posix.c	Sun Jun 18 00:05:46 2006
+++ guile-core.nd/libguile/posix.c	Tue Aug 22 13:42:17 2006
 <at>  <at>  -942,7 +942,11  <at>  <at> 
   scm_dynwind_unwind_handler (free_string_pointers, exec_argv, 
 			    SCM_F_WIND_EXPLICITLY);

-  execv (exec_file, exec_argv);
+  execv (exec_file,
+#ifdef __MINGW32__
+	(const char * const *)
+#endif
+	exec_argv);
   SCM_SYSERROR;

   /* not reached.  */
 <at>  <at>  -973,7 +977,11  <at>  <at> 
   scm_dynwind_unwind_handler (free_string_pointers, exec_argv, 
 			    SCM_F_WIND_EXPLICITLY);

-  execvp (exec_file, exec_argv);
(Continue reading)

percy tiglao | 27 Aug 2006 19:31
Picon

Minor documentation layout flaws

Hello. I decided to make a print version of the reference manual; but
there were so many stuff that ran through the right side of the page
(technically, overfull hboxes). I'm interested in helping you guys
remove those things so that all the stuff fits on a page; but I'm
wondering if there are any standards and such before I start making
major changes.

For example: one of the pages had some guile source code with
"call-with-current-continuation" on it. But the word was so big; that
it pushed the parameters off the page. The easiest correction is to
just change the word into "call/cc" instead; but that might conflict
with your standard...

So I'm just wondering if you got anything like that. If not... I'll be
working on that documentation patch!

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Kevin Ryde | 28 Aug 2006 23:51
Picon
Picon

Re: Minor documentation layout flaws

"percy tiglao" <prtiglao <at> gmail.com> writes:
>
> overfull hboxes

If tex would report them in a form that you could step through it'd be
possible to fix the worst ones.

> "call-with-current-continuation" on it. But the word was so big; that
> it pushed the parameters off the page.

Thanks, I reformatted a bit.

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

percy tiglao | 29 Aug 2006 01:10
Picon

Re: Minor documentation layout flaws

On 8/28/06, Kevin Ryde <user42 <at> zip.com.au> wrote:
> "percy tiglao" <prtiglao <at> gmail.com> writes:
> >
> > overfull hboxes
>
> If tex would report them in a form that you could step through it'd be
> possible to fix the worst ones.

Actually; it does.

After you do texi2dvi, all the overful hboxes are in "guile.log" (assuming
you did "texi2dvi guile.texi")

The bigger the number (ex: overful hbox: 500pt) the worse it is.

_______________________________________________
Bug-guile mailing list
Bug-guile <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


Gmane