X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f Message-Id: <464b00a6$0$4613$61c65585@un-2park-reader-01.sydney.pipenetworks.com.au> From: caddit Subject: Re: Using libxml2 with DJGPP Newsgroups: comp.os.msdos.djgpp Date: Wed, 16 May 2007 23:01:02 +1000 References: <46476A40 DOT 2040707 AT schluessler DOT org> <464879E4 DOT 3030300 AT schluessler DOT org> Organization: caddit.net User-Agent: KNode/0.10.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Lines: 27 NNTP-Posting-Host: 220.233.177.46 X-Trace: 1179320486 un-2park-reader-01.sydney.pipenetworks.com.au 4613 220.233.177.46:52582 X-Complaints-To: Abuse, including message IDs to abuse AT pipenetworks DOT com To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi Timo. > Now I know that i have to use the wingnu bash and wingnu make and all > theese gnu windows programm to compile libxml2 for DJGPP (not as i did > it with native linux, what makes no sense). And when i have all the gnu > functions for win, i can compile iconv too. I'm not sure I correctly understood all that. Please be sure that *you* understand what DJGPP 2.04 is: a development *platform*. *Mixing* platforms is generally a *very* bad idea for any kind of development environment. I.E. you would never try to run a complex DOS batchfile straight from a UNIX shell, or expect winsock.dll to run linux networking. They come from incompatible OSes and different *platforms*. In summary, for each platform you want to develop you need the developer's toolchain for *that* platform. DJGPP has it's own bash, perl, gawk, sed, autoconf, gcc and related libraries. Windows has a different set, Cygwin has another, Wattcom another, etc. You generally don't mix them. Even toolchain components from different *versions* of the *same* platform (i.e. DJGPP 2.03 vs. DJGPP 2.04) shouldn't be mixed at risk of major borkage unless you know what you're doing. Regards, Ben