Well, on my system (Ubuntu 14.04 LTS) it is a no= n-trivial task to get the Debian package for guile 2.0.11 without contamina= ting my package manager with (incompatible) upstream libraries.

The obvious solution would be to set up a virtual machine to continue, bu= t sadly my current hardware doesn't support that...

Since = I appear to be the only one affected by this issue, I guess only thing I ca= n do is try to get set up with a different machine...

On Mon, Jul 27, 2015 at 5:2= 1 AM, Vladimir Zhbanov (vzhbanov AT gmai= l.com) [via geda-user AT delorie.= com] <geda-user AT delorie DOT com> wrote:

On Sun, Jul 26, 2015 at 09:30:48PM -0400= , Jason White (whitewa= terssoftwareinfo AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> It must be specific to my distro's version of guile. Xubuntu 14.04= .
> When I type guile, I see "GNU Guile 2.0.9"
>
Hmm, the current Debian stable version of guile is 2.0.11, and Debia= n is
rather conservative distribution. Could you update your guile version?

And then, try to build as follows:

sudo make uninstall
git pull
make maintainer-clean && ./autogen.sh && ./configure &&= amp; make && sudo make install && sudo ldconfig

> find /usr | grep guile | grep [18]; yields no interesting results
> not a trace guile 1.8 to be found on my system.
>
>
> What I did to test:
>
> Untinstalled guile-1.8,
>
> ./configure
> make clean
> make
> ./gschem -> Error remains
>
> Applied patch, the files also had missing.h
>
> gschem/src/gschem_coord_dialog.c:23:#include <missing.h>
> gschem/src/gschem_arc_dialog.c:23:#include <missing.h>
> gschem/src/gschem_slot_edit_dialog.c:23:#include <missing.h>
> gschem/src/gschem_about_dialog.c:23:#include <missing.h>
> gschem/src/gschem_close_confirmation_dialog.c:23:#include <missing.= h>
> gschem/src/gschem_hotkey_dialog.c:23:#include <missing.h>
> gschem_translate_dialog.c:23:#include <missing.h>
This is because my patch is probably older than edits in those files= . So
it has become incomplete now.

>
> ./configure
> make clean
> make
> ./gschem -> Error remains
>
> Error:
>
> Backtrace:
> In ice-9/boot-9.scm:
>=C2=A0 157: 1 [catch #t #<catch-closure 9463370> ...]
> In unknown file:
>=C2=A0 =C2=A0 ?: 0 [apply-smob/1 #<catch-closure 9463370>]
>
> ERROR: In procedure apply-smob/1:
> ERROR: In procedure scm_to_utf8_stringn: Wrong type argument in
> position 1 (expecting string): #f

I saw this before while trying to cross-compile for Windows.

The only place the scm_to_utf8_stringn function is used after applying
my patch, as I see it, is in the string->page code. Could you run your gschem in a clean environment to exclude issues with your rc settings?

Cheers,
=C2=A0 Vladimir

Jason White

--001a11c1fbbe57312a051dc7b99e--