On Mon, Jan 01, 2007 at 07:32:51PM -0800, Jim Wilson wrote:
> This is the wrong part of the config.log fragment. The interesting part
> is nearer the top, immediately after the command using the -V option.
> The use of -V probably fails which is OK as this is only for information
> purposes, but t
On Mon, 2007-01-01 at 18:19 -0800, Douglas B Rupp wrote:
> Would you like the complete config.log by private email?
Sure.
> config.log fragment
This is the wrong part of the config.log fragment. The interesting part
is nearer the top, immediately after the command using the -V option.
The use o
On Mon, Jan 01, 2007 at 06:19:08PM -0800, Douglas B Rupp wrote:
> configure:4811: /home/rupp/ngnat/buildxppcaix/./gcc/xgcc
> -B/home/rupp/ngnat/buildxppcaix/./gcc/
> -B/home/rupp/gnat/powerpc-ibm-aix5.2.0.0/bin/
> -B/home/rupp/gnat/powerpc-ibm-aix5.2.0.0/lib/ -isystem
> /home/rupp/gnat/powerpc-
Jim Wilson wrote:
Douglas B Rupp wrote:
I'm happy to try writing a patch, but my version of gcc/configure
doesn't look like what you described.
I tried a build with the gcc-4.1.x branch, and gcc/nm is computed
correctly, so the problem I described on mainline does not exist here.
Unfortunate
Douglas B Rupp wrote:
I'm happy to try writing a patch, but my version of gcc/configure
doesn't look like what you described.
I tried a build with the gcc-4.1.x branch, and gcc/nm is computed
correctly, so the problem I described on mainline does not exist here.
Unfortunately, I wasn't able t
Douglas B Rupp wrote:
I'm happy to try writing a patch, but my version of gcc/configure
doesn't look like what you described.
I updated my tree, and configure still looks the same, then I realized
that you are using a branch. My mistake. So the problem I described is
still there on mainline
Daniel Jacobowitz wrote:
I'm not at all sure how the nm failure ends up leading to this problem,
but I'll take your word for that part.
I should have explained that part. I got an error from nm as invoked by
collect. nm failed because gcc/nm in the build tree is a shell script
that does 'ex
Douglas B Rupp wrote:
I'm happy to try writing a patch, but my version of gcc/configure
doesn't look like what you described.
I forgot to svn update my tree. It was older than I thought. I'll have
to update it and try again.
Did you try looking in the config.log file as I described? What
Did someone forget to tell you that AIX 4.3 and above are not really
supported by the GNU binutils anyways? So it is kinda of useless to
have a cross compiler which does not work anyways :).
I emailed the maintainer on this subject when I started this project but
never got a reply. It seems
>
> Jim Wilson wrote:
> > Inside the gcc configure,
> > we do "test -x $NM_FOR_TARGET" and this fails because NM_FOR_TARGET
> > expands to more than a program name, and the shell test -x command does
> > not handle this case. We need to extract out the program name for this
> > test. This sho
Jim Wilson wrote:
Inside the gcc configure,
we do "test -x $NM_FOR_TARGET" and this fails because NM_FOR_TARGET
expands to more than a program name, and the shell test -x command does
not handle this case. We need to extract out the program name for this
test. This should be easy enough to d
On Sun, Dec 31, 2006 at 06:12:23PM -0800, Jim Wilson wrote:
> Admittedly, the configure error printed is a bit misleading. It used to
> make sense when it was first written, but a lot of stuff has changed
> since then, and the error message never got updated.
The GCC_NO_EXECUTABLES error messag
Douglas B Rupp wrote:
checking for library containing strerror... configure: error: Link tests
are not allowed after GCC_NO_EXECUTABLES.
You get this error if a link command fails while trying to configure the
target libiberty. So the question is why did the link fail? You need
to look at t
> Newlib targets are targets without their own native libc. I find it
> exceedingly hard to believe that AIX falls into this category.
Newlib supports some platforms that have their own native libc.
Douglas B Rupp writes:
> Andrew Haley wrote:
> > Douglas B Rupp writes:
> > > DJ Delorie wrote:
> > > > Is your target a newlib target? If so, are you including
> > --with-newlib?
> > > >
> > >
> > > Thanks, that was the problem.
> > > Why isn't --with-newlib the default for newl
Andrew Haley wrote:
Douglas B Rupp writes:
> DJ Delorie wrote:
> > Is your target a newlib target? If so, are you including --with-newlib?
> >
>
> Thanks, that was the problem.
> Why isn't --with-newlib the default for newlib targets?
AIX is a newlib target? Really?
Andrew.
Don't
Douglas B Rupp writes:
> DJ Delorie wrote:
> > Is your target a newlib target? If so, are you including --with-newlib?
> >
>
> Thanks, that was the problem.
> Why isn't --with-newlib the default for newlib targets?
AIX is a newlib target? Really?
Andrew.
DJ Delorie wrote:
Why isn't --with-newlib the default for newlib targets?
--with-newlib *tells* us that it's a newlib target.
Well not knowing what a newlib target was when you asked, I looked in
configure.in.
It seems that if it's not a newlib target then target-newlib is missing
from n
> Why isn't --with-newlib the default for newlib targets?
--with-newlib *tells* us that it's a newlib target.
DJ Delorie wrote:
Is your target a newlib target? If so, are you including --with-newlib?
Thanks, that was the problem.
Why isn't --with-newlib the default for newlib targets?
Is your target a newlib target? If so, are you including --with-newlib?
21 matches
Mail list logo
