Mail Archives: djgpp-workers/2009/09/05/13:54:17
This is a multi-part message in MIME format.
--------------050907030606030600060401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
09/04/2009 05:15 PM, Rugxulo kirjoitti:
> Hi, :-)
>
> On Fri, Sep 4, 2009 at 5:31 AM, Eli Zaretskii<eliz AT gnu DOT org> wrote:
>
>> Can someone build the latest GDB CVS snapshots with DJGPP?
>>
>
> I personally could probably try later if you really really needed me
> to, but I've never built GDB before so I'm a little hesitant.
> Hopefully Andris can squeeze in a compile or two for you. :-)
>
>
I'm not sure. Currently I have here Windows Vista only. DJGPP port of
bash does not work very nice under Windows Vista. Strange but I
succeeded to build GCC-4.4.1 once with port of bash-2.05b, but not later
after that. So later I had to use last build of bash-2.04 from
current/v2gnu. I could guess that crashes both when building GDB-7.0pre
under WinXP and also what I have experienced under Windows Vista
represents real problems with DJGPP port of bash. Of course NTVDM crash
is not the how it should have been handled. We cannot however expect
much more than now from Microsoft.
Of of possible way could also be cross-building GDB from for example
Linux. I have tried it sometimes long time ago and it worked, but I had
to give some hints for configure. The same way may have be possible also
now.
>> They switched to a newer version of Autotools, where the parts of the
>> configure script that are run each time it tries to compile a program
>> were replaced with a shell function ac_fn_c_try_compile.
>>
>
> It's supposed to be much faster this way (e.g. Cygwin -> 30% speed increase).
>
>
>> The DJGPP port of Bash crashes while running this function, at least on XP,
>> where I have my DJGPP development environment installed.
>>
>> If no one can suggest a workaround for this (e.g., by some editing of
>> the configure scripts or by some change in the development
>> environment), I guess this will be the end of the way for the DJGPP
>> port of GDB, because I will not have time and resources to debug Bash
>> and fix it any time soon. That would mean all the efforts I invested
>> in bringing the DJGPP GDB back to life would be lost, and GDB 7.0, to
>> be released soon, will not support a DJGPP build.
>>
>> Any help is greatly appreciated.
>>
>
> Wow, you sound exasperated! Yes, it's a very annoying bug, and
> apparently it's existed since 2004 (hi, Gordon!). No fix yet (Bash
> source is confusing!), but we do mostly know where the problem lies.
>
> http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/08/16:37:27
> http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/20/11:54:36
> http://lists.gnu.org/archive/html/bug-autoconf/2009-08/msg00066.html
>
> For now, I suggest the wonderful workaround of putting "( " and " )"
> around the "return $ac_retval" portions. That seems to make it work
> for DJGPP Bash, at least. (I guess you didn't notice my similar issue
> when ZILE upgraded to AutoConf 2.64, heh.)
>
>
--------------050907030606030600060401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
09/04/2009 05:15 PM, Rugxulo kirjoitti:
<blockquote
cite="mid:93c172b50909040715n791c007ema4715db95e946e2e AT mail DOT gmail DOT com"
type="cite">
<pre wrap="">Hi, :-)
On Fri, Sep 4, 2009 at 5:31 AM, Eli Zaretskii<a
class="moz-txt-link-rfc2396E" href="mailto:eliz AT gnu DOT org"><eliz AT gnu DOT org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Can someone build the latest GDB CVS snapshots with DJGPP?
</pre>
</blockquote>
<pre wrap=""><!---->
I personally could probably try later if you really really needed me
to, but I've never built GDB before so I'm a little hesitant.
Hopefully Andris can squeeze in a compile or two for you. :-)
</pre>
</blockquote>
I'm not sure. Currently I have here Windows Vista only. DJGPP port of
bash does not work very nice under Windows Vista. Strange but I
succeeded to build GCC-4.4.1 once with port of bash-2.05b, but not
later after that. So later I had to use last build of bash-2.04 from
current/v2gnu. I could guess that crashes both when building GDB-7.0pre
under WinXP and also what I have experienced under Windows Vista
represents real problems with DJGPP port of bash. Of course NTVDM crash
is not the how it should have been handled. We cannot however expect
much more than now from Microsoft.<br>
<br>
Of of possible way could also be cross-building GDB from for example
Linux. I have tried it sometimes long time ago and it worked, but I had
to give some hints for configure. The same way may have be possible
also now. <br>
<blockquote
cite="mid:93c172b50909040715n791c007ema4715db95e946e2e AT mail DOT gmail DOT com"
type="cite">
<blockquote type="cite">
<pre wrap="">They switched to a newer version of Autotools, where the parts of the
configure script that are run each time it tries to compile a program
were replaced with a shell function ac_fn_c_try_compile.
</pre>
</blockquote>
<pre wrap=""><!---->
It's supposed to be much faster this way (e.g. Cygwin -> 30% speed increase).
</pre>
<blockquote type="cite">
<pre wrap="">The DJGPP port of Bash crashes while running this function, at least on XP,
where I have my DJGPP development environment installed.
If no one can suggest a workaround for this (e.g., by some editing of
the configure scripts or by some change in the development
environment), I guess this will be the end of the way for the DJGPP
port of GDB, because I will not have time and resources to debug Bash
and fix it any time soon. That would mean all the efforts I invested
in bringing the DJGPP GDB back to life would be lost, and GDB 7.0, to
be released soon, will not support a DJGPP build.
Any help is greatly appreciated.
</pre>
</blockquote>
<pre wrap=""><!---->
Wow, you sound exasperated! Yes, it's a very annoying bug, and
apparently it's existed since 2004 (hi, Gordon!). No fix yet (Bash
source is confusing!), but we do mostly know where the problem lies.
<a class="moz-txt-link-freetext"
href="http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/08/16:37:27">http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/08/16:37:27</a>
<a class="moz-txt-link-freetext"
href="http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/20/11:54:36">http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp/2006/08/20/11:54:36</a>
<a class="moz-txt-link-freetext"
href="http://lists.gnu.org/archive/html/bug-autoconf/2009-08/msg00066.html">http://lists.gnu.org/archive/html/bug-autoconf/2009-08/msg00066.html</a>
For now, I suggest the wonderful workaround of putting "( " and " )"
around the "return $ac_retval" portions. That seems to make it work
for DJGPP Bash, at least. (I guess you didn't notice my similar issue
when ZILE upgraded to AutoConf 2.64, heh.)
</pre>
</blockquote>
<br>
</body>
</html>
--------------050907030606030600060401--
- Raw text -