From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Another cross-compiler problem! Date: 12 Oct 2001 10:41:36 GMT Organization: Aachen University of Technology (RWTH) Lines: 38 Message-ID: <9q6hd0$f21$1@nets3.rz.RWTH-Aachen.DE> References: <20011012100040 DOT 47703 DOT qmail AT web9105 DOT mail DOT yahoo DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1002883296 15425 137.226.32.75 (12 Oct 2001 10:41:36 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 12 Oct 2001 10:41:36 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com ROLAND wrote: > I still have problems. I get 'type clashes'??? What can I do about > this. We don't know --- you provided far too less information for any sensible advice to be given. We'ld at the very least need the exact compiler error messages, and a meaningful code snipped that triggered them. > Also my compiler is falling on the next piece of code: > typedef struct outfileset { > char *filename; > u_long loadstart, > loadend, > carrstart; > struct outfileset *nextfile; > } OUTFLSET > It tells me that it has a parse error before u_long. Impossible to diagnose, too --- you don't show enough context, nor the exact error message from your compiler. Most importantly, there is no definition of u_long in sight, so it's impossible for anybody but you to check what might be wrong with it. > And last, I need a header to replace my sparc's sgtty.h, the header > should be used on a PC. You should ask this in a Unix programming newsgroup, not here. AFAIK, is a rather oldfashioned, now deprecated part of Unix systems. On this Digital Unix system here, e.g., all it really does is #include . IOW: your program probably had better not use on the Solaris end, either. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.