public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: problem building 6.1 for powerpc on cygwin
Date: Wed, 02 Jun 2004 17:21:00 -0000	[thread overview]
Message-ID: <1086196961.2747.16.camel@lindt.uglyboxes.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

[Copy for the list]

-----Forwarded Message-----
From: Marc Schafer <mschafer@avidyne.com>
To: Keith Seitz <keiths@redhat.com>
Subject: Re: problem building 6.1 for powerpc on cygwin
Date: Wed, 02 Jun 2004 10:12:09 -0700

configure doesn't seem to do much.  i guess most of it happens when
you do a make?

i did this:
../insight-6.1/configure --prefix=/usr/local/ppctools --target=powerpc
-eabi >& config.out

I am pretty sure that my cross compiler is working (powerpc-eabi-gcc
3.4.0).

I looked here for a snapshot to try:
ftp://sources.redhat.com/pub/gdb/snapshots/current/

The newest insight snapshot seems to be from April.  Am I looking the
wrong place?

thanks for all your help,
marc



----- Original Message ----- 
From: "Keith Seitz" <keiths@redhat.com>
To: "Marc Schafer" <mschafer@avidyne.com>
Cc: <insight@sources.redhat.com>
Sent: Wednesday, June 02, 2004 9:31 AM
Subject: Re: problem building 6.1 for powerpc on cygwin


> On Wed, 2004-06-02 at 08:31, Marc Schafer wrote:
> > I am trying to build insight 6.1 for powerpc-eabi but it is
failing in
> > the tk build.  It appears that it is looking for X.  I have built
> > older versions under cygwin and I thought X was not required.  It
> > generates hundreds of errors, but here is a snippet.
>
> You are correct: X is not required for cygwin, and it does look like
it
> is looking for X stuff.
>
> Do you have the output of your run of configure?
>
> I'm pretty sure that I've built this within the last few weeks...
Maybe
> a snapshot would be worth investigating?
>
> Keith
>
>

[-- Attachment #2: config.log --]
[-- Type: application/octet-stream, Size: 1447 bytes --]

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:583: checking host system type
configure:604: checking target system type
configure:622: checking build system type
configure:677: checking for a BSD compatible install
configure:2856: checking for i686-pc-cygwin-ar
configure:2889: checking for ar
configure:2928: checking for i686-pc-cygwin-as
configure:2961: checking for as
configure:3000: checking for i686-pc-cygwin-dlltool
configure:3033: checking for dlltool
configure:3072: checking for i686-pc-cygwin-ld
configure:3144: checking for i686-pc-cygwin-nm
configure:3177: checking for nm
configure:3216: checking for i686-pc-cygwin-ranlib
configure:3249: checking for ranlib
configure:3288: checking for i686-pc-cygwin-windres
configure:3321: checking for windres
configure:3360: checking for i686-pc-cygwin-objcopy
configure:3393: checking for objcopy
configure:3432: checking for i686-pc-cygwin-objdump
configure:3465: checking for objdump
configure:3514: checking for powerpc-eabi-ar
configure:3586: checking for powerpc-eabi-as
configure:3658: checking for powerpc-eabi-dlltool
configure:3730: checking for powerpc-eabi-ld
configure:3802: checking for powerpc-eabi-nm
configure:3874: checking for powerpc-eabi-ranlib
configure:3946: checking for powerpc-eabi-windres
configure:4046: checking whether to enable maintainer-specific portions of Makefiles

[-- Attachment #3: config.out --]
[-- Type: application/octet-stream, Size: 1358 bytes --]

creating cache ./config.cache
checking host system type... i686-pc-cygwin
checking target system type... powerpc-unknown-eabi
checking build system type... i686-pc-cygwin
checking for a BSD compatible install... /bin/install -c
checking for i686-pc-cygwin-ar... no
checking for ar... ar
checking for i686-pc-cygwin-as... no
checking for as... as
checking for i686-pc-cygwin-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-cygwin-ld... /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld.exe
checking for i686-pc-cygwin-nm... no
checking for nm... nm
checking for i686-pc-cygwin-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-cygwin-windres... no
checking for windres... windres
checking for i686-pc-cygwin-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-cygwin-objdump... no
checking for objdump... objdump
checking for powerpc-eabi-ar... powerpc-eabi-ar
checking for powerpc-eabi-as... powerpc-eabi-as
checking for powerpc-eabi-dlltool... no
checking for powerpc-eabi-ld... powerpc-eabi-ld
checking for powerpc-eabi-nm... powerpc-eabi-nm
checking for powerpc-eabi-ranlib... powerpc-eabi-ranlib
checking for powerpc-eabi-windres... no
checking whether to enable maintainer-specific portions of Makefiles... no
updating cache ./config.cache
creating ./config.status
creating Makefile

             reply	other threads:[~2004-06-02 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 17:21 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-02 15:31 Marc Schafer
2004-06-02 16:30 ` Keith Seitz
     [not found]   ` <04a101c448c4$bd2c6650$0b01a8c0@maestrale>
2004-06-02 17:21     ` Keith Seitz
2004-06-03  2:00       ` Stephen & Linda Smith
     [not found]         ` <001a01c44916$481e7400$6501a8c0@canoli>
2004-06-03  3:23           ` Stephen & Linda Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1086196961.2747.16.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).