X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <4141e908$0$175$cc7c7865@news.luth.se>
From: Martin Str|mberg <ams AT speedy DOT ludd DOT ltu DOT se>
Subject: Re: compiling djgpp: which gcc?
Newsgroups: comp.os.msdos.djgpp
References: <20040909150711 DOT GC9890 AT webhome DOT cz> <mbr2k0tcd4k1a7de9lhev6j6jr0k5gictq AT 4ax DOT com> <20040910130940 DOT GD21756 AT webhome DOT cz>
User-Agent: tin/1.4.6-20020816 ("Aerials") (UNIX) (NetBSD/1.6Q (alpha))
Date: 10 Sep 2004 17:48:56 GMT
Lines: 53
NNTP-Posting-Host: speedy.ludd.ltu.se
X-Trace: 1094838536 news.luth.se 175 130.240.16.13
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Egon Eckert <egon AT heaven DOT industries DOT cz> wrote:
> Thanks for your lonely reply!  Probably other developers became afraid
> to have to help me compile the whole suite, which may not be a task
> for everyone...

Nope. We don't have time to follow this newsgroup 100%. And if you
wanted to talk to the DJGPP developers, you should use the
djgpp-workers mailing list.

Perhaps it's been too long or I've done it so many times, but I think
it very easy to compile libc. Just unzip the source and go down into
src and type "make".

> I will have to study the thing a lot before I could even think of
> contributing.  I really don't want to ask beginner's questions here...

This is where beginners' questions should be made. However beginners'
questions regarding libc implementation or compiling are better posted
to djgpp-workers and are welcome there.

But you should check the FAQ first before posting to any list/group.
Common DJGPP problems are in the FAQ. There is a document with advice
for djgpp-workers in the DJGPP Knowledge Base (which you reach with
"info kb devel").

Anyway there is very little activity on djgpp-workers as almost none
have any time for it anymore. So we welcome anyone that want to
correct bugs.

As a matter of fact I think there have been some patches some people
contributed that I think is good and should be applied but nobody has
had time to do that. This isn't meant to put you off. I'm just trying
to show you how badly little time there is.

> Yesterday I finally remained stuck unable to link something because of
> the recent (_)environ changes--the symbol should be provided through a
> change in "djgpp.djl" linker script, but the linker is instructed to
> use a lib/gcc-lib/.../djgpp-x.djl instead, which doesn't have the
> needed PROVIDE directive, but when I replace it with the djgpp.djl CVS
> version, the linker chokes on it (parse error on new "LONG(0)" line),

Hmm... We'll see what my ancient setup thinks about that (when I get
time...).

> so...  It's a black magic.  Now I see the truth: don't help me, I'm
> not worth it! :-))

See above.


Right,

						MartinS