From: "David Zhang" <davidzhl@hotmail.com>
To: nickc@cambridge.redhat.com
Cc: binutils@sources.redhat.com
Subject: Re: problem of porting gas
Date: Wed, 27 Mar 2002 06:53:00 -0000 [thread overview]
Message-ID: <F158PmmUHs4SVGg3i5F0000e013@hotmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 3333 bytes --]
Hi Nick,
>In which case are you running 'configure' from the top level of the source
directory, or from inside the gas subdirectory ? If the former then you
probably want to edit the "config.sub" file to add your target.
I do configure in the gas subdirectory.
>If this does not help, perhaps you could send me a (small) copy of the
command you are running and its output.
---------------------------------------------------------
[root@zl gas]# pwd
/root/binutils-2.11.2/gas
[root@zl gas]# autoconf
[root@zl gas]# automake
automake: Makefile.am: not supported: source file `config/m68k-parse.y' is
in subdirectory
[root@zl gas]# ./configure --target=mipsx3
loading cache ./config.cache
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
checking host system type... i686-pc-linux-gnu
checking target system type... Invalid configuration `mipsx3': machine
`mipsx3' not recognized
checking build system type... i686-pc-linux-gnu
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for POSIXized ISC... no
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for /usr/bin/ld option to reload object files... (cached) -r
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking how to recognise dependant libraries... (cached) pass_all
checking for object suffix... (cached) o
checking for executable suffix... (cached) no
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
loading cache ./config.cache within ltconfig
checking whether -lc should be explicitly linked in... (cached) no
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... (cached) yes
checking if gcc static flag -static works... (cached) yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
creating libtool
loading cache ./config.cache
configure: error: GAS does not know what format to use for target
_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄ Web µç×ÓÓʼþϵͳ ¡ª¡ª MSN Hotmail¡£
http://www.hotmail.com/cn
next reply other threads:[~2002-03-27 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 6:53 David Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 19:15 David Zhang
2002-03-27 4:27 David Zhang
2002-03-27 6:40 ` Nick Clifton
2002-03-27 1:09 David zhang
2002-03-27 1:25 ` Nick Clifton
2002-03-27 7:21 ` 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=F158PmmUHs4SVGg3i5F0000e013@hotmail.com \
--to=davidzhl@hotmail.com \
--cc=binutils@sources.redhat.com \
--cc=nickc@cambridge.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).