public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "ariga masahiro" <ariga@link-lab.co.jp>
To: <ecos-discuss@sources.redhat.com>,
	        "Dave Lawrence" <dlawrence@ad-holdings.co.uk>
Subject: Re: [ECOS]  Re: Wrongfully compiled code
Date: Tue, 12 Feb 2008 01:06:00 -0000	[thread overview]
Message-ID: <000801c86d13$785aec50$1c0110ac@ariga> (raw)
In-Reply-To: <47A6F914.4010400@ad-holdings.co.uk>

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

Hello,Dave,and others,

Thanks to you,
as I applied patch that you taught me,I cleared next error.
> checking for shared libgcc... configure: error: Link tests are not

I exulted and expected to succeed,but lastly(I hope)
there happened next error.

checking for C compiler default output file name... configure: error: C 
compiler
 cannot create executables
See `config.log' for more details.
make[1]: *** [configure-target-libssp] Error 1
make[1]: Leaving directory `/tmp/build/build_gcc'
make: *** [all] Error 2
make: Leaving directory `/tmp/build/build_gcc'

I searched among many config.logs and found that
\tmp\build\build_gcc\sh-elf\m2a\libssp\config.log
contained above error message.

It says,

configure:2274: $? = 0
configure:2276: 
/tmp/build/build_gcc/./gcc/xgcc -B/tmp/build/build_gcc/./gcc/ -nostdinc -B/tmp/build/build_gcc/sh-elf/m2a/newlib/ 
 -isystem /tmp/build/build_gcc/sh-elf/m2a/newlib/targ-include -isystem 
/usr/local/sh-elf/gcc-4.1.1/newlib/libc/include -B/usr/local/sh-elf/sh-elf/bin/ 
 -B/usr/local/sh-elf/sh-elf/lib/ -isystem 
/usr/local/sh-elf/sh-elf/include -isystem 
/usr/local/sh-elf/sh-elf/sys-include  -m2a -v </dev/null >&5
Reading specs from /tmp/build/build_gcc/./gcc/specs
Target: sh-elf
Configured with: 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --host=i686-pc-cygwin  
--build=i686-pc-cygwin --prefix=/usr/local/sh-elf --enable-languages=c,c++ --with-gnu-as 
 --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v : (reconfigured) 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --host=i686-pc-cygwin  
--build=i686-pc-cygwin --prefix=/usr/local/sh-elf --enable-languages=c,c++ --with-gnu-as 
 --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v : (reconfigured) 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --host=i686-pc-cygwin  
--build=i686-pc-cygwin --prefix=/usr/local/sh-elf --enable-languages=c,c++ --with-gnu-as 
 --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v : (reconfigured) 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --host=i686-pc-cygwin  
--build=i686-pc-cygwin --prefix=/usr/local/sh-elf --enable-languages=c,c++ --with-gnu-as 
 --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v : (reconfigured) 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --prefix=/usr/local/sh-elf 
 --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v : (reconfigured) 
/usr/local/sh-elf/gcc-4.1.1/configure --target=sh-elf --prefix=/usr/local/sh-elf 
 --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v
Thread model: single
gcc version 4.1.1
configure:2279: $? = 0
configure:2281: 
/tmp/build/build_gcc/./gcc/xgcc -B/tmp/build/build_gcc/./gcc/ -nostdinc -B/tmp/build/build_gcc/sh-elf/m2a/newlib/ 
 -isystem /tmp/build/build_gcc/sh-elf/m2a/newlib/targ-include -isystem 
/usr/local/sh-elf/gcc-4.1.1/newlib/libc/include -B/usr/local/sh-elf/sh-elf/bin/ 
 -B/usr/local/sh-elf/sh-elf/lib/ -isystem 
/usr/local/sh-elf/sh-elf/include -isystem 
/usr/local/sh-elf/sh-elf/sys-include  -m2a -V </dev/null >&5
xgcc: '-V' must come at the start of the command line
configure:2284: $? = 1
configure:2307: checking for C compiler default output file name
configure:2310: 
/tmp/build/build_gcc/./gcc/xgcc -B/tmp/build/build_gcc/./gcc/ -nostdinc -B/tmp/build/build_gcc/sh-elf/m2a/newlib/ 
 -isystem /tmp/build/build_gcc/sh-elf/m2a/newlib/targ-include -isystem 
/usr/local/sh-elf/gcc-4.1.1/newlib/libc/include -B/usr/local/sh-elf/sh-elf/bin/ 
 -B/usr/local/sh-elf/sh-elf/lib/ -isystem 
/usr/local/sh-elf/sh-elf/include -isystem 
/usr/local/sh-elf/sh-elf/sys-include  -m2a -O2 -O2    conftest.c  >&5
/tmp/build/build_gcc/sh-elf/m2a/newlib/libc.a: could not read symbols: 
Archive has no index; run ranlib to add one
collect2: ld returned 1 exit status
configure:2313: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "libssp"
| #define PACKAGE_TARNAME "libssp"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "libssp 1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "libssp"
| #define VERSION "1.0"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2352: error: C compiler cannot create executables
See `config.log' for more details.

I also noticed other config.logs relating to  each libssp directories
contained error messages like next.
---
conftest.c:2: error: expected '=', ',', ';', 'asm' or '__attribute__' before 
'me'
configure:2749: $? = 1
configure: failed program was:
| #ifndef __cplusplus
|   choke me
| #endif

configure:2893: checking for style of include used by make
conftest.c:11:28: error: ac_nonexistent.h: No such file or directory
configure:3256: $? = 1
configure: failed program was:
| /* confdefs.h.  */
---
I do not know why it happened,and what I should do,
would you please help me ?

I append the same config.log and build logs "configgcc.txt","makegcc.txt" in 
tar.bz2 format.

Below are my shell scripts.
===============================================
[setup.sh]
export TARGET=sh-elf
export PREFIX=/usr/local/sh-elf
export CFLAGS="-O2"
export CXXFLAGS="-O2"
export CFLAGS_FOR_TARGET="-Os"
export CXXFLAGS_FOR_TARGET="Os"
===============================================
[appendpath.sh]
PATH=$PATH:/usr/local/sh-elf/bin
===============================================
I separated building shell script.
[buildgcc-1.sh]
/usr/local/sh-elf/gcc-4.1.1/configure --target=$TARGET --prefix=$PREFIX --enable-languages=c,c++ 
 --with-gnu-as --with-gnu-ld --with-newlib --with-ggxx-include-dir=/usr/local/sh-elf/sh-elf/include 
 --with-ecos -v  2>&1 | tee configgcc.txt

[buildgcc-2.sh]
make clean
make -w all install 2>&1 | tee makegcc.txt
===============================================
I am very much obliged to your help.
Thank you in advance.

Masahiro Ariga

[-- Attachment #2: log_files.tar.bz2 --]
[-- Type: application/octet-stream, Size: 51368 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-02-12  1:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 23:59 [ECOS] " ariga masahiro
2008-01-08  0:05 ` Gary Thomas
2008-01-08  1:05   ` ariga masahiro
2008-01-17 19:21     ` [ECOS] " Dave Lawrence
2008-01-17 23:50       ` ariga masahiro
2008-01-18 12:16         ` Dave Lawrence
2008-01-18 14:40           ` Gregg Levine
2008-01-18 15:44             ` Dave Lawrence
2008-01-18 15:49               ` Gregg Levine
2008-01-18 16:09                 ` Dave Lawrence
2008-01-21  0:34           ` ariga masahiro
2008-02-04  1:49           ` ariga masahiro
2008-02-04 11:38             ` Dave Lawrence
2008-02-12  1:06               ` ariga masahiro [this message]
2008-02-12 10:55                 ` Dave Lawrence
2008-02-22  4:57   ` [ECOS] How to re-install newly compiled gnutools ariga masahiro
2008-02-22  7:15     ` ariga masahiro
2008-05-16  8:13       ` [ECOS] When or on what condition does "deschedule" happen? ariga masahiro
2008-05-16 15:26         ` Andrew Lunn
2008-05-19  5:32           ` ariga masahiro
2008-05-19 13:18             ` Andrew Lunn
2008-05-19 13:31               ` Gary Thomas
2008-05-20  1:26               ` ariga masahiro
2008-05-20 12:18                 ` Andrew Lunn
2008-05-23  7:38                   ` ariga masahiro
2008-05-23  9:35                     ` Nick Garnett
     [not found]                   ` <000601c8c165$406e0970$1c0110ac@ariga>
2008-05-29 18:23                     ` [ECOS] Re: In trouble of timer operations Andrew Lunn
2008-05-30  2:50                       ` ariga masahiro
2008-05-30  3:09                         ` Paul D. DeRocco
2008-05-30  4:11                           ` ariga masahiro
2008-05-30  4:43                             ` Paul D. DeRocco
2008-05-30  7:26                               ` ariga masahiro
2008-05-30  7:47                                 ` Paul D. DeRocco
2008-05-30  8:03                                   ` ariga masahiro
2008-05-30  8:07                                 ` Andrew Lunn
2008-06-04  5:25                                   ` ariga masahiro
2008-06-04 10:06                                     ` Paul D. DeRocco
2008-06-05  6:14                                       ` ariga masahiro
2008-06-05 17:39                                         ` Paul D. DeRocco
2008-05-30  6:35                             ` Andrew Lunn

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='000801c86d13$785aec50$1c0110ac@ariga' \
    --to=ariga@link-lab.co.jp \
    --cc=dlawrence@ad-holdings.co.uk \
    --cc=ecos-discuss@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).