3:38 p.m.
I wrote:
so i'm trying to get xemacs to build, and configure decides
it's ok to build
modules, but when it tries to build them, it throws up at the module-link
stage,
with a zillion undefined references:
Frank writes:
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.xemacs.design,gmane.emacs.xemacs.beta as
well.
"Ben Wing" <ben(a)xemacs.org> writes:
> so i'm trying to get xemacs to build, and configure decides
it's ok to build
> modules, but when it tries to build them, it throws up at the module-link
stage,
> with a zillion undefined references:
>[...]
>> This is under the very latest of Cygwins:
>>
>> /src/xemacs/lilfix/nt 2052$ uname -a
>> CYGWIN_NT-5.0 NEEEEEEE 1.3.13(0.62/3/2) 2002-10-13 23:15 i686 unknown
>
>This might be one reason for your errors, I heard may people complaining
>1.3.13 would be extremely broken. Perhaps you should try a recent snapshot
>of 1.3.14 and see if it helps.
well, i did upgrade, but it didn't help -- not surprisingly since this is a gcc
problem not a core problem.
however, cygwin did upgrade very recently to gcc 3. anyone else having success
[or problems] with gcc 3?
btw frank, if you mirror between mailing lists and internal newsgroups, you
should really come up with a way of hiding this, so that when people get sent
"courtesy copies", they appear with the original mailing lists in the header
instead of the internal newsgroup names.
ben
3:47 p.m.
New subject: module problems on cygwin
"Ben Wing" <ben(a)xemacs.org> writes:
btw frank, if you mirror between mailing lists and internal
newsgroups, you
should really come up with a way of hiding this, so that when people get sent
"courtesy copies", they appear with the original mailing lists in the header
instead of the internal newsgroup names.
Amazing, it worked very well until now, I'll have to do some
testing. (The problem seems to be the added CC header, perhaps I should
use BCC to hide it from the mail2news and back gateway, gmane.org the
best thing since sliced bread).
BTW: You stated once, that you'd like a copy to your personal address,
is this till valid or can I just stop it?
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
2:42 a.m.
New subject: module problems on cygwin
----- Original Message -----
From: "Andy Piper" <andy(a)xemacs.org>
To: "Ben Wing" <ben(a)xemacs.org>; "XEmacs beta list"
<xemacs-beta(a)xemacs.org>;
"XEmacs Design" <xemacs-design(a)xemacs.org>; "Jerry James"
<james(a)xemacs.org>;
<jkj(a)sco.com>
Sent: Sunday, October 27, 2002 9:49 AM
Subject: RE: module problems on cygwin
> however, cygwin did upgrade very recently to gcc 3. anyone
else
> having success
> [or problems] with gcc 3?
You can still get gcc2 - I use that for all the binary kits.
do you have problems building on cygwin using gcc 3? if not, does your build
try to build the postgres code?
3:17 a.m.
New subject: module problems on cygwin
do you have problems building on cygwin using gcc 3? if not,
does your build
try to build the postgres code?
I don't use gcc3 - I usee gcc2 and have no problems (well other than the
infinite dumping problem which I still don't have a good solution for).
andy
10:31 a.m.
New subject: module problems on cygwin
----- Original Message -----
From: "Andy Piper" <andy(a)xemacs.org>
To: "Ben Wing" <ben(a)666.com>; "XEmacs beta list"
<xemacs-beta(a)xemacs.org>;
"XEmacs Design" <xemacs-design(a)xemacs.org>; "Jerry James"
<james(a)xemacs.org>;
<jkj(a)sco.com>
Sent: Sunday, October 27, 2002 8:17 PM
Subject: RE: module problems on cygwin
> do you have problems building on cygwin using gcc 3? if not,
> does your build
> try to build the postgres code?
I don't use gcc3 - I usee gcc2 and have no problems (well other than the
infinite dumping problem which I still don't have a good solution for).
which problem?
andy
4:17 a.m.
New subject: module problems on cygwin
> I don't use gcc3 - I usee gcc2 and have no problems (well other than the
> infinite dumping problem which I still don't have a good solution for).
which problem?
If I try and build 21.5 the dump phase goes into an endless loop, I presume
because there is some transient memory spike which causes the static heap to
be size incorrectly. I can only get around this by setting the gc threshold
insanely low.
andy
4:23 a.m.
New subject: module problems on cygwin
>>>> "Ben" == Ben Wing <ben(a)xemacs.org>
writes:
Ben> however, cygwin did upgrade very recently to gcc 3. anyone
Ben> else having success [or problems] with gcc 3?
GCC 3 and/or glibc 2.2.5 seem to be associated with problems on Red
Hat and SuSE. Very vague feeling, but only getting such reports from
people on the bleeding edge.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
8053
days inactive
8062
days old
7 comments
5 participants
participants (5)
-
Andy Piper -
Ben Wing -
Ben Wing -
Frank Schmitt -
Stephen J. Turnbull