This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: problem compiling binutils 2.10
- To: Alan Modra <alan at linuxcare dot com dot au>
- Subject: Re: problem compiling binutils 2.10
- From: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- Date: Wed, 28 Jun 2000 09:01:13 -0500
- CC: Heiko Nardmann <h dot nardmann at secunet dot de>, binutils at sourceware dot cygnus dot com
- Organization: OAR Corporation
- References: <Pine.LNX.4.21.0006281850330.27908-100000@front.linuxcare.com.au>
- Reply-To: joel dot sherrill at OARcorp dot com
Alan Modra wrote:
>
> On Wed, 28 Jun 2000, Heiko Nardmann wrote:
>
> > COMPUNIT is a define in /usr/include/compunit.h:
> > So do I have to insert a include statement somewhere? If yes where is it best?
>
> No. HPUX:/usr/include/compunit.h is probably included from one of the
> other HPUX:/usr/include/*.h files, and you are quite likely to need that
> one too. The trouble is going to be that even if you figure out exactly
> which header files must be pulled in from HP-UX, it's likely that at least
> some of them will clash with header files on your native system. I wish
> you luck!
If you want to fix this long term, why not create the files and
add them to binutils. Start by creating empty versions of all
the missing files. Then see what types/structures/defines the
code really needs. Add them to your empty files until it compiles.
Don't add anything that is not needed.
Someone else will have to speak about keeping the new files
clean enough to make them suitable for inclusion in binutils.
> Alan Modra
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985