[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem is CC environment var. (was Re: Something screwed up in PROJECT_ROOT or PROJECT_TOPdir)
- Date: Mon, 21 Feb 2005 17:21:25 +0100
- From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
- Subject: Re: Problem is CC environment var. (was Re: Something screwed up in PROJECT_ROOT or PROJECT_TOPdir)
On Mon, 2005-02-21 at 09:52 -0500, Peter Dufault wrote:
> On Feb 21, 2005, at 8:08 AM, Ralf Corsepius wrote:
> > ... I would not exclude handling of CC to be broken in RTEMS toplevel
> > configure script, but similar to other problems you are reporting, I
> > can't reproduce them, nor am I aware of any problem related to setting
> > up CC.
> I'll set up a Linux system to try to reproduce them. As I said, maybe
> the GNU M4 stack corruption is present but not being detected - it is
> stackovf.c detecting the stack corruption and aborting.
> I applied the automake patch, which is still required in the very
> latest automake, that bug report should be updated to point that out.
The patch is in automake CVS head (aka. automake-1.10), the current
version is 1.9.5.
> Unfortunately I still can't build without --enable-multilib after
> getting rid of "CC" and applying the automake patch - I still wind up
> with the -isystem headers in the wrong place in the tree, one level too
> What is your top_builddir, MULTIBUILDTOP and PROJECT_INCLUDE in your
> Makefile if you build, for example, "psim" without --enable-multilib?
> I wind up with:
> top_builddir = .
> MULTIBUILDTOP =
> PROJECT_INCLUDE =
<path>/rtems/configure --target=powerpc-rtems4.7 \
and send me your
on PM (bzip'ed please :-) ).
[rsp. powerpc-rtems*, if you're using --target=powerpc-rtems]