Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Kirkpatrick <tom@settopsolutions.com>
To: gdb@sourceware.org
Cc: Tom Kirkpatrick <tom@settopsolutions.com>
Subject: GCC_NO_EXECUTABLES
Date: Tue, 14 Nov 2006 09:05:00 -0000	[thread overview]
Message-ID: <D7179E62-06BA-433D-85F4-4BC328A4BBBE@settopsolutions.com> (raw)

Hi,

I'm trying to cross-compile gdb 6.4 for an x86 target but do not seem  
to be able to get past configuration, which dies with the following:

| NOTE: make SUBDIRS=intl mmalloc libiberty opcodes bfd sim gdb etc  
utils
| make[1]: Entering directory `/home/tom/stv/oe-stv/build/tmp-stv/ 
work/i586-stv-linux/gdb-6.4-r0/build-i586-stv-linux'
| mkdir -p -- ./libiberty
| Configuring in ./libiberty
| configure: loading site script /home/tom/stv/oe-stv/ 
org.openembedded.dev/site/i586-linux
| configure: creating cache ./config.cache
| checking whether to enable maintainer-specific portions of  
Makefiles... no
| checking for makeinfo... makeinfo --split-size=5000000
| checking for perl... perl
| checking build system type... i686-pc-linux-gnu
| checking host system type... i586-stv-linux-gnu
| checking for i586-stv-linux-ar... i586-stv-linux-ar
| checking for i586-stv-linux-ranlib... i586-stv-linux-ranlib
| checking for i586-stv-linux-gcc... ccache i586-stv-linux-gcc-3.4.4 - 
march=c3 -mtune=c3
| checking for suffix of object files... o
| checking whether we are using the GNU C compiler... yes
| checking whether ccache i586-stv-linux-gcc-3.4.4 -march=c3 - 
mtune=c3 accepts -g... yes
| checking for ccache i586-stv-linux-gcc-3.4.4 -march=c3 -mtune=c3  
option to accept ANSI C... none needed
| checking how to run the C preprocessor... i586-stv-linux-gcc-3.4.4 -E
| checking whether ccache i586-stv-linux-gcc-3.4.4 -march=c3 - 
mtune=c3 and cc understand -c and -o together... yes
| checking for an ANSI C-conforming const... yes
| checking for inline... inline
| checking whether byte ordering is bigendian... (cached) no
| checking for a BSD-compatible install... /usr/bin/install -c
| checking for sys/file.h... yes
| checking for sys/param.h... yes
| checking for limits.h... yes
| checking for stdlib.h... yes
| checking for malloc.h... yes
| checking for string.h... yes
| checking for unistd.h... yes
| checking for strings.h... yes
| checking for sys/time.h... yes
| checking for time.h... yes
| checking for sys/resource.h... yes
| checking for sys/stat.h... yes
| checking for sys/mman.h... yes
| checking for fcntl.h... yes
| checking for alloca.h... yes
| checking for sys/pstat.h... no
| checking for sys/sysmp.h... no
| checking for sys/sysinfo.h... yes
| checking for machine/hal_sysinfo.h... no
| checking for sys/table.h... no
| checking for sys/sysctl.h... yes
| checking for sys/systemcfg.h... no
| checking for stdint.h... yes
| checking for stdio_ext.h... yes
| checking for sys/wait.h that is POSIX.1 compatible... yes
| checking whether time.h and sys/time.h may both be included... yes
| checking whether errno must be declared... no
| checking for egrep... grep -E
| checking for ANSI C header files... yes
| checking for sys/types.h... yes
| checking for sys/stat.h... (cached) yes
| checking for stdlib.h... (cached) yes
| checking for string.h... (cached) yes
| checking for memory.h... yes
| checking for strings.h... (cached) yes
| checking for inttypes.h... yes
| checking for stdint.h... (cached) yes
| checking for unistd.h... (cached) yes
| checking for int... yes
| checking size of int... (cached) 4
| checking for uintptr_t... yes
| checking for a 64-bit type... uint64_t
| checking for pid_t... yes
| checking for library containing strerror... configure: error: Link  
tests are not allowed after GCC_NO_EXECUTABLES.
| make[1]: *** [configure-libiberty] Error 1

I get the same error when trying 6.3 too.  Has anyone seen this before?

many thanks
Tom


             reply	other threads:[~2006-11-14  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14  9:05 Tom Kirkpatrick [this message]
2006-11-14 13:52 ` GCC_NO_EXECUTABLES Daniel Jacobowitz

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=D7179E62-06BA-433D-85F4-4BC328A4BBBE@settopsolutions.com \
    --to=tom@settopsolutions.com \
    --cc=gdb@sourceware.org \
    /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