There's no documentation on layout: you pick the prefix, and the tools put
things where they want them within that space in accordance with GNU/FHS
practices.  If you want specific pieces somewhere else, you'll have to
specify that with the configure options.

Perhaps you're somehow picking up pieces from an old version due to your
path or other environment settings.  Try doing a bare "gcc -v -c test.c"
where test.c does nothing but include <io.h>.  Make sure the paths in the
subcommands make sense given your installation.

Peter

On Fri, Jul 22, 2011 at 6:56 AM, Bob von Knobloch <b...@vknobloch.de> wrote:

> On 22/07/11 12:15, Peter Bigot wrote:
> > On Thu, Jul 21, 2011 at 11:00 AM, bob <b...@vknobloch.de> wrote:
> >> I followed the readme exactly. I have what appears to be a sensible
> >> directory structure (although I note the is no 'info' or 'man'
> >> directory, as there was in the '4' version).
> >
> > If you want those, you have to run the make commands that build and
> > install them, same as with any other source installation.
> >
> >>>>        main.c:24:16: fatal error: io.h: No such file or directory
> >> I want to correct the paths etc. and will do so once I have built the
> >> tools successfully. Until then  can anyone suggest what is wrong here?
> >
> > No.  Find where io.h got put (it comes from msp430mcu), and if it's in
> > the same place as the other msp430 headers (${prefix}/msp430/include)
> > figure out what's in your CFLAGS or environment that's keeping it from
> > being found.  If it's not there, figure out what went wrong with the
> > invocation of install.sh.  It may be an Opensuse issue.
> >
> > I still look forward to your bug report explaining why all the paths are
> wrong.
> >
> > Peter
> >
> Thank you, at least I know now where io.h *should* be (and it is).
>
> Is there a doc. outlining the required directory structure anywhere?
> And also the location of the correct man/info stuff?
>
> Bob
>
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Web Security
> Learn 10 ways to better secure your business today. Topics covered include:
> Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
> security Microsoft Exchange, secure Instant Messaging, and much more.
> http://www.accelacomm.com/jaw/sfnl/114/51426210/
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
------------------------------------------------------------------------------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to