unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "objc" <objcjohn@hotmail.com>
To: "Andy Wingo" <wingo@pobox.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: guile 2.0.9 build on mingw
Date: Mon, 20 May 2013 22:09:59 +0100	[thread overview]
Message-ID: <BAY178-DS1396D534DB3C160878524EC8AF0@phx.gbl> (raw)
In-Reply-To: <874ndx9y7h.fsf@pobox.com>

Hi Eli,

I've seen problems like this too.
  GEN    guile-procedures.texi
Throw without catch before boot:

You have to build guile.exe properly before guile-procedures.texi etc...
 works because guile.exe  (guilec.exe) builds them.

To get the build right, I change ports.c print.c and strings .c
92: //jrg\f
#define iconv_open libiconv_open
#define iconv libiconv
#define iconv_close libiconv_close
//end jrg

print.c:
*******
59://jrg
#define iconv_open libiconv_open
#define iconv libiconv
#define iconv_close libiconv_close
//end jrg

strings.h
*********
1946:  const char *jrgbuf;//jrg
1993:  jrgbuf = NULL;
1996://  if (enc == NULL)
//    enc = "ISO-8859-1";
  if (enc == NULL) enc = "ANSI_X3.4-1968";    //jrg
  if (scm_i_is_narrow_string (str))
    {
	  jrgbuf = scm_i_string_chars (str);     //jrg
//      fprintf (stderr,"jrgbuf 
[%s]ilen[%d]encoding[%s]enc[%s]lenp[%d]\n",jrgbuf,ilen,encoding,enc,(int)(size_t 
 )lenp);//jrg
      ret = mem_iconveh (jrgbuf, ilen,
                         "ANSI_X3.4-1968", enc,//"ANSI_X3.4-1968" 
"ISO-8859-1" "UTF-8"
                         (enum iconv_ilseq_handler) handler, NULL,
                         &buf, &len);

      if (ret != 0)
      {//jrg
      //try another one !!
//      fprintf (stderr,"try ISO-8859-1 jrgbuf 
[%s]ilen[%d]encoding[%s]enc[%s]lenp[%d]\n",jrgbuf,ilen,encoding,enc,(int)(size_t 
 )lenp);//jrg
      ret = mem_iconveh (jrgbuf, ilen,
                         "ISO-8859-1", enc,//"ANSI_X3.4-1968"  "ISO-8859-1" 
"UTF-8"
                         (enum iconv_ilseq_handler) handler, NULL,
                         &buf, &len);
      }
      if (ret != 0)
      {//jrg
      //try another one !!
//      fprintf (stderr,"try UTF-8jrgbuf 
[%s]ilen[%d]encoding[%s]enc[%s]lenp[%d]\n",jrgbuf,ilen,encoding,enc,(int)(size_t 
 )lenp);//jrg
      ret = mem_iconveh (jrgbuf, ilen,
                         "UTF-8", enc,//"ANSI_X3.4-1968"  "ISO-8859-1" 
"UTF-8"
                         (enum iconv_ilseq_handler) handler, NULL,
                         &buf, &len);
      }
      if (ret != 0)
      {//jrg

        printf("(ret != 0) jrgbuf [%s] buf[%s]\n",jrgbuf,buf);//jrg
       fprintf (stderr,"failed return jrgbuf jrgbuf 
[%s]ilen[%d]encoding[%s]enc[%s]lenp[%d]\n",jrgbuf,ilen,encoding,enc,(int)(size_t 
 )lenp);//jrg
        return (char*)jrgbuf;//hmmm

        scm_encoding_error (__func__, errno,
			    "cannot convert narrow string to output locale",
			    SCM_BOOL_F,
			    /* FIXME: Faulty character unknown.  */
			    SCM_BOOL_F);
	  }//jrg
    }
  else
    {
	  jrgbuf = (char *)(scm_t_uint32 *) scm_i_string_wide_chars (str); 
//jrg
	  fprintf (stderr,"jrgbuf 
[%s]ilen[%d]encoding[%s]enc[%s]lenp[%d]\n",jrgbuf,ilen,encoding,enc,(int)(size_t 
 )lenp);//jrg
      buf = u32_conv_to_encoding (enc,
                                  (enum iconv_ilseq_handler) handler,
                                  (scm_t_uint32 *) scm_i_string_wide_chars 
(str),
                                  ilen,
                                  NULL,
                                  NULL, &len);
      if (buf == NULL)
      {//jrg
        printf("(buf == NULL) jrgbuf [%s] buf [%s]\n",jrgbuf,buf);//jrg
        scm_encoding_error (__func__, errno,
			    "cannot convert wide string to output locale",
			    SCM_BOOL_F,
			    /* FIXME: Faulty character unknown.  */
			    SCM_BOOL_F);
	  }
    }

This is just some hacking around, but may put someone on the right track.

I use cygwin (mingw) on XP SP3 (see http://branch-twigg.webs.com/       for 
my build).
It's still buggy but does what I need it to do.

Hope this helps.

John Goodwin
--------------------------------------------------
From: "Andy Wingo" <wingo@pobox.com>
Sent: Monday, May 20, 2013 9:46 PM
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: <guile-user@gnu.org>
Subject: Re: guile 2.0.9 build on mingw

> On Mon 20 May 2013 22:05, Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Mon, 20 May 2013 21:46:02 +0200
>>> From: Panicz Maciej Godek <godek.maciek@gmail.com>
>>>
>>> I'm trying to build guile on mingw, but i get the following error:
>>>
>>> the instruction at 0x7059fe6b refrenced memory at 0x00000004 the memory
>>> could not be read
>>>
>>> The error appears at the stage
>>>
>>>   GEN      guile-procedures.texi
>>>
>>> but when I ask make to keep going, the same error appears when guilec 
>>> tries
>>> to compile ice-9/eval.go.
>>
>> I reported a similar problem here:
>>
>>   http://lists.gnu.org/archive/html/bug-guile/2013-05/msg00006.html
>>
>> So far no replies.  I hope to hear from them some day.
>
> Thanks for the ping :)  Can you run meta/gdb-uninstalled-guile and get a
> backtrace somehow?  Do you know what source line this error is coming
> from?  I've only cross-built and not actually tried to run Guile on
> native MinGW.
>
> Andy
> -- 
> http://wingolog.org/
>
> 



  reply	other threads:[~2013-05-20 21:09 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 19:46 guile 2.0.9 build on mingw Panicz Maciej Godek
2013-05-20 20:05 ` Eli Zaretskii
2013-05-20 20:46   ` Andy Wingo
2013-05-20 21:09     ` objc [this message]
2013-05-21  2:43       ` Eli Zaretskii
2013-05-22 15:26     ` Eli Zaretskii
2013-06-07  8:37       ` Eli Zaretskii
2013-06-07 12:44       ` Ludovic Courtès
2013-06-07 14:59         ` Eli Zaretskii
2013-06-09 17:10           ` Eli Zaretskii
2013-06-09 20:33             ` Ludovic Courtès
2013-06-09 21:16               ` Andy Wingo
2013-06-09 21:35                 ` Ludovic Courtès
2013-06-10 16:18                   ` Eli Zaretskii
2013-06-10 16:18                 ` Eli Zaretskii
2013-06-10 16:23               ` Eli Zaretskii
2013-06-10 19:09                 ` Mark H Weaver
2013-06-10 19:49                   ` Eli Zaretskii
2013-06-10 20:54                     ` Mark H Weaver
2013-06-11 16:53                       ` Eli Zaretskii
2013-06-11 22:11                         ` Ludovic Courtès
2013-06-12 17:46                           ` Eli Zaretskii
2013-06-18 21:51                             ` Why launch the Guile signal delivery thread on exit? (was Re: guile 2.0.9 build on mingw) Mark H Weaver
2013-06-19 15:51                               ` Eli Zaretskii
2013-06-19 16:06                               ` Julian Graham
2013-06-19 19:20                               ` Ludovic Courtès
2013-06-12 17:57                         ` guile 2.0.9 build on mingw Eli Zaretskii
2013-06-13 13:26                           ` Eli Zaretskii
2013-06-16 14:19                             ` Ludovic Courtès
2013-06-13 13:33                           ` Eli Zaretskii
2013-06-16 14:36                             ` Ludovic Courtès
2013-06-16 15:40                               ` Eli Zaretskii
2013-06-16 14:55                             ` Ludovic Courtès
2013-06-16 15:47                               ` Eli Zaretskii
2013-06-16 18:59                                 ` Ludovic Courtès
2013-06-13 13:40                           ` Eli Zaretskii
2013-06-16 14:59                             ` Ludovic Courtès
2013-06-17 15:41                               ` Eli Zaretskii
2013-06-18 20:45                                 ` Ludovic Courtès
2013-06-18 22:28                                   ` Mark H Weaver
2013-06-19  3:03                                     ` Eli Zaretskii
2013-06-19 19:26                                     ` Ludovic Courtès
2013-06-19 20:02                                       ` Eli Zaretskii
2013-06-19  2:59                                   ` Eli Zaretskii
2013-06-19 15:56                                   ` Eli Zaretskii
2013-06-19 19:38                                     ` Ludovic Courtès
2013-06-13 13:41                           ` Eli Zaretskii
2013-06-16 15:04                             ` Ludovic Courtès
2013-06-16 15:48                               ` Eli Zaretskii
2013-06-16 14:44                           ` Ludovic Courtès
2013-06-16 15:41                             ` Eli Zaretskii
2013-06-12 17:59                         ` Eli Zaretskii
2013-06-16 14:46                           ` Ludovic Courtès
2013-06-12 18:02                         ` Eli Zaretskii
2013-06-16 19:50                           ` Ludovic Courtès
2013-06-16 20:22                             ` Eli Zaretskii
2013-06-17 15:45                           ` Mark H Weaver
2013-06-18 17:17                             ` Eli Zaretskii
2013-06-18 19:31                               ` Eli Zaretskii
2013-06-18 20:19                                 ` Ludovic Courtès
2013-06-19  2:53                                   ` Eli Zaretskii
2013-06-19 19:28                                     ` Ludovic Courtès
2013-06-19 19:56                                       ` Eli Zaretskii
2013-05-26 20:41     ` Panicz Maciej Godek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY178-DS1396D534DB3C160878524EC8AF0@phx.gbl \
    --to=objcjohn@hotmail.com \
    --cc=eliz@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).