public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
* ct-ng, arm, newlib build error
@ 2010-01-15 10:49 Jonathan Cameron
  2010-01-15 18:03 ` Yann E. MORIN
  0 siblings, 1 reply; 5+ messages in thread
From: Jonathan Cameron @ 2010-01-15 10:49 UTC (permalink / raw)
  To: crossgcc; +Cc: yann.morin.1998

Dear All,

Has anyone seen this problem? It is occurring on one of my two machines (gentoo box
running pretty recent versions of everything).  This problem occured with
the current mercurial tree.

[INFO ]  =================================================================
[INFO ]  Installing C library
[ERROR]    /home/jic23/src/toolchain/bob/targets/src/newlib-1.18.0/newlib/libc/search/hash_page.c:176: internal compiler error: in default_secondary_reload, at targhooks.c:660
[ERROR]    make[6]: *** [lib_a-hash_page.o] Error 1
[ERROR]    make[5]: *** [all-recursive] Error 1
[ERROR]    make[4]: *** [all-recursive] Error 1
[ERROR]    make[3]: *** [all] Error 2
[ERROR]    make[2]: *** [all-target-newlib] Error 2
[ERROR]    make[1]: *** [all] Error 2
[ERROR]    Build failed in step 'Installing C library'
[ERROR]    Error happened in '/usr/local/lib/ct-ng-hg_default@1725_dbd5078816f9/scripts/functions' in function 'CT_DoExecLog' (line unknown, sorry)
[ERROR]          called from '/usr/local/lib/ct-ng-hg_default@1725_dbd5078816f9/scripts/build/libc/newlib.sh' at line # 81 in function 'do_libc'
[ERROR]          called from '/usr/local/lib/ct-ng-hg_default@1725_dbd5078816f9/scripts/crosstool-NG.sh' at line # 553 in function 'main'
[ERROR]    Look at '/home/jic23/x-tools/arm-at91sam7_nommu-eabi/build.log' for more info on this error.
[ERROR]  (elapsed: 14:22.50)
[14:30] / make: *** [build] Error 2


.config is below.

I'm not particularly familiar with ct-ng so please ask if more info is needed.

Thanks,

Jonathan


#
# Automatically generated make config: don't edit
# crosstool-NG version: hg_default@1725_dbd5078816f9
# Thu Jan 14 19:34:28 2010
#

#
# Paths and misc options
#

#
# crosstool-NG behavior
#
# CT_OBSOLETE is not set
CT_EXPERIMENTAL=y
# CT_DEBUG_CT is not set

#
# Paths
#
CT_LOCAL_TARBALLS_DIR=""
CT_WORK_DIR="${CT_TOP_DIR}/targets"
CT_PREFIX_DIR="${HOME}/x-tools/${CT_TARGET}"
CT_INSTALL_DIR="${CT_PREFIX_DIR}"
CT_REMOVE_DOCS=y
CT_INSTALL_DIR_RO=y

#
# Downloading
#
# CT_FORBID_DOWNLOAD is not set
# CT_FORCE_DOWNLOAD is not set
# CT_USE_MIRROR is not set
CT_CONNECT_TIMEOUT=10
CT_DOWNLOAD_MAX_CHUNKS=5
# CT_ONLY_DOWNLOAD is not set

#
# Extracting
#
# CT_FORCE_EXTRACT is not set
CT_OVERIDE_CONFIG_GUESS_SUB=y
# CT_ONLY_EXTRACT is not set
CT_PATCH_BUNDLED=y
# CT_PATCH_LOCAL is not set
# CT_PATCH_BUNDLED_LOCAL is not set
# CT_PATCH_LOCAL_BUNDLED is not set
# CT_PATCH_BUNDLED_FALLBACK_LOCAL is not set
# CT_PATCH_LOCAL_FALLBACK_BUNDLED is not set
# CT_PATCH_NONE is not set
CT_PATCH_ORDER="bundled"
# CT_PATCH_SINGLE is not set
# CT_PATCH_USE_LOCAL is not set

#
# Build behavior
#
CT_PARALLEL_JOBS=1
CT_LOAD=0
CT_NICE=0
CT_USE_PIPES=y
# CT_CONFIG_SHELL_SH is not set
# CT_CONFIG_SHELL_ASH is not set
CT_CONFIG_SHELL_BASH=y
# CT_CONFIG_SHELL_CUSTOM is not set
CT_CONFIG_SHELL="bash"

#
# Logging
#
# CT_LOG_ERROR is not set
# CT_LOG_WARN is not set
CT_LOG_INFO=y
# CT_LOG_EXTRA is not set
# CT_LOG_DEBUG is not set
# CT_LOG_ALL is not set
CT_LOG_LEVEL_MAX="INFO"
# CT_LOG_SEE_TOOLS_WARN is not set
CT_LOG_PROGRESS_BAR=y
CT_LOG_TO_FILE=y
CT_LOG_FILE_COMPRESS=y

#
# Target options
#
CT_ARCH="arm"
CT_ARCH_SUPPORTS_BOTH_MMU=y
CT_ARCH_SUPPORTS_BOTH_ENDIAN=y
CT_ARCH_SUPPORTS_32=y
# CT_ARCH_SUPPORTS_64 is not set
CT_ARCH_SUPPORT_ARCH=y
# CT_ARCH_SUPPORT_ABI is not set
CT_ARCH_SUPPORT_CPU=y
CT_ARCH_SUPPORT_TUNE=y
CT_ARCH_SUPPORT_FPU=y
CT_ARCH_DEFAULT_HAS_MMU=y
# CT_ARCH_DEFAULT_BE is not set
CT_ARCH_DEFAULT_LE=y
CT_ARCH_DEFAULT_32=y
# CT_ARCH_DEFAULT_64 is not set
CT_ARCH_ARCH=""
CT_ARCH_CPU=""
CT_ARCH_TUNE=""
CT_ARCH_FPU=""
# CT_ARCH_BE is not set
CT_ARCH_LE=y
CT_ARCH_32=y
# CT_ARCH_64 is not set
CT_ARCH_BITNESS=32
CT_ARCH_FLOAT_HW=y
# CT_ARCH_FLOAT_SW is not set
CT_TARGET_CFLAGS=""
CT_TARGET_LDFLAGS=""

#
# General target options
#
# CT_ARCH_alpha is not set
CT_ARCH_arm=y
# CT_ARCH_avr32 is not set
# CT_ARCH_ia64 is not set
# CT_ARCH_mips is not set
# CT_ARCH_powerpc is not set
# CT_ARCH_s390 is not set
# CT_ARCH_sh is not set
# CT_ARCH_x86 is not set
CT_ARCH_ARM_MODE="thumb"
# CT_ARCH_ARM_MODE_ARM is not set
CT_ARCH_ARM_MODE_THUMB=y
# CT_ARCH_ARM_INTERWORKING is not set
CT_ARCH_ARM_EABI=y
# CT_ARCH_USE_MMU is not set

#
# Target optimisations
#

#
# Toolchain options
#

#
# General toolchain options
#
CT_USE_SYSROOT=y
CT_SYSROOT_DIR_PREFIX=""

#
# Tuple completion and aliasing
#
CT_TARGET_VENDOR="at91sam7_nommu"
CT_TARGET_ALIAS_SED_EXPR=""
CT_TARGET_ALIAS=""

#
# Toolchain type
#
# CT_NATIVE is not set
CT_CROSS=y
# CT_CROSS_NATIVE is not set
# CT_CANADIAN is not set
CT_TOOLCHAIN_TYPE="cross"

#
# Build system
#
CT_BUILD=""
CT_BUILD_PREFIX=""
CT_BUILD_SUFFIX=""

#
# Operating System
#
CT_BARE_METAL=y
# CT_KERNEL_SUPPORTS_SHARED_LIBS is not set
CT_KERNEL="bare-metal"
CT_KERNEL_bare_metal=y
# CT_KERNEL_linux is not set

#
# Common kernel options
#

#
# Binary utilities
#
# CT_ARCH_BINFMT_ELF is not set
CT_ARCH_BINFMT_FLAT=y

#
# GNU binutils
#
CT_BINUTILS_V_2_20=y
# CT_BINUTILS_V_2_19_1 is not set
# CT_BINUTILS_V_2_19 is not set
# CT_BINUTILS_V_2_18 is not set
# CT_BINUTILS_V_2_17 is not set
# CT_BINUTILS_V_2_16_1 is not set
CT_BINUTILS_VERSION="2.20"
CT_BINUTILS_EXTRA_CONFIG=""

#
# elf2flt
#
CT_ELF2FLT_CVSHEAD=y
# CT_ELF2FLT_CVS_SNAPSHOT is not set
CT_ELF2FLT_VERSION="head"
CT_ELF2FLT_EXTRA_CONFIG=""

#
# C compiler
#
CT_CC="gcc"
CT_CC_VERSION="4.4.2"
CT_CC_gcc=y
CT_CC_V_4_4_2=y
# CT_CC_V_4_4_1 is not set
# CT_CC_V_4_4_0 is not set
# CT_CC_V_4_3_4 is not set
# CT_CC_V_4_3_3 is not set
# CT_CC_V_4_3_2 is not set
# CT_CC_V_4_3_1 is not set
# CT_CC_V_4_3_0 is not set
# CT_CC_V_4_2_4 is not set
# CT_CC_V_4_2_3 is not set
# CT_CC_V_4_2_2 is not set
# CT_CC_V_4_2_1 is not set
# CT_CC_V_4_2_0 is not set
# CT_CC_V_4_1_2 is not set
# CT_CC_V_4_0_4 is not set
# CT_CC_V_3_4_6 is not set
CT_CC_GCC_4_3_or_later=y
CT_CC_GCC_4_4_or_later=y
CT_CC_ENABLE_CXX_FLAGS=""
CT_CC_CORE_EXTRA_CONFIG=""
CT_CC_PKGVERSION="crosstool-NG-${CT_VERSION}"
CT_CC_BUGURL=""
CT_CC_SUPPORT_CXX=y
CT_CC_SUPPORT_FORTRAN=y
CT_CC_SUPPORT_JAVA=y
CT_CC_SUPPORT_ADA=y
CT_CC_SUPPORT_OBJC=y
CT_CC_SUPPORT_OBJCXX=y

#
# Additional supported languages:
#
# CT_CC_LANG_CXX is not set

#
# C-library
#
CT_LIBC="newlib"
CT_LIBC_VERSION=""
# CT_LIBC_eglibc is not set
# CT_LIBC_glibc is not set
CT_LIBC_newlib=y
# CT_LIBC_none is not set
# CT_LIBC_uClibc is not set
# CT_LIBC_NEWLIB_V_1_18_0 is not set
# CT_LIBC_NEWLIB_V_1_17_0 is not set
CT_LIBC_NEWLIB_CVS=y

#
# Architecture specific options
#
# CT_LIBC_SUPPORT_NPTL is not set
# CT_LIBC_SUPPORT_LINUXTHREADS is not set
CT_THREADS="none"

#
# Common C library options
#
# CT_THREADS_NPTL is not set
# CT_THREADS_LINUXTHREADS is not set
CT_THREADS_NONE=y

#
# Debug facilities
#
# CT_DEBUG_dmalloc is not set
# CT_DEBUG_duma is not set
CT_DEBUG_gdb=y
CT_GDB_CROSS=y
# CT_GDB_CROSS_STATIC is not set
# CT_GDB_CROSS_INSIGHT is not set

#
# In bare-metal, you'll need to   
#

#
# provide your own gdbserver stub.
#
CT_GDB_V_7_0_1=y
# CT_GDB_V_7_0 is not set
# CT_GDB_V_6_8 is not set
# CT_GDB_V_snapshot is not set
CT_GDB_VERSION="7.0.1"
# CT_DEBUG_ltrace is not set
# CT_DEBUG_strace is not set

#
# Tools facilities
#
# CT_TOOL_libelf is not set
# CT_TOOL_sstrip is not set

#
# Companion libraries
#
CT_WRAPPER_NEEDED=y
CT_GMP_MPFR=y
CT_GMP_V_4_3_1=y
# CT_GMP_V_4_3_0 is not set
# CT_GMP_V_4_2_4 is not set
# CT_GMP_V_4_2_2 is not set
CT_GMP_VERSION="4.3.1"
CT_MPFR_V_2_4_2=y
# CT_MPFR_V_2_4_1 is not set
# CT_MPFR_V_2_4_0 is not set
# CT_MPFR_V_2_3_2 is not set
# CT_MPFR_V_2_3_1 is not set
CT_MPFR_VERSION="2.4.2"
CT_PPL_CLOOG_MPC=y
CT_PPL_V_0_10_2=y
CT_PPL_VERSION="0.10.2"
CT_CLOOG_V_0_15_7=y
# CT_CLOOG_V_0_15_6 is not set
# CT_CLOOG_V_0_15_5 is not set
# CT_CLOOG_V_0_15_4 is not set
# CT_CLOOG_V_0_15_3 is not set
CT_CLOOG_VERSION="0.15.7"
CT_MPC_V_0_8_1=y
# CT_MPC_V_0_7 is not set
# CT_MPC_V_0_6 is not set
CT_MPC_VERSION="0.8.1"

#
# Companion libraries common options
#
# CT_COMP_LIBS_CHECK is not set
CT_TOOLS_WRAPPER_SCRIPT=y
# CT_TOOLS_WRAPPER_EXEC is not set
CT_TOOLS_WRAPPER="script"

--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ct-ng, arm, newlib build error
  2010-01-15 10:49 ct-ng, arm, newlib build error Jonathan Cameron
@ 2010-01-15 18:03 ` Yann E. MORIN
  2010-01-15 18:58   ` Jonathan Cameron
  0 siblings, 1 reply; 5+ messages in thread
From: Yann E. MORIN @ 2010-01-15 18:03 UTC (permalink / raw)
  To: Jonathan Cameron; +Cc: crossgcc

Jonathan, All,

On Friday 15 January 2010 11:51:04 Jonathan Cameron wrote:
> Has anyone seen this problem? It is occurring on one of my two machines
> (gentoo box running pretty recent versions of everything).

And does it work on the other machine?

> This problem 
> occured with the current mercurial tree.

I see you're using newlib-1.18.0. It's been only recently introduced, and
I haven't had time to play with it yet.

Also, as stated in the TODO at the root of the crosstool-NG tree:
---8<---
- update newlib (for enhanced bare metal)
  - confirm existing implementation on targets other than AVR32
  - try to make it generic, will help for uClibc++
---8<---

Which should be obvious that newlib support is kind of Work In Progress.
It is currently really EXPERIMENTAL. I managed to build a newlib-based
arm toolchain, and you should start off with it:

# ct-ng show-arm-bare_newlib_cortex_m3_nommu-eabi
arm-bare_newlib_cortex_m3_nommu-eabi  [l X]
    OS            : bare-metal
    GMP/MPFR      : gmp-4.3.1 / mpfr-2.4.1
    PPL/CLOOG/MPC : ppl-0.10.2 / cloog-0.15.7 / mpc-0.7
    binutils      : binutils-2.19.1
    C compiler    : gcc-4.4.1 (C,C++)
    C library     : newlib
    Tools         :

As you already experienced, be prepared fro breakage, though...

> [ERROR]    Error happened in '/usr/local/lib/ct-ng-hg_default@1725_dbd5078816f9/scripts/functions' in function 'CT_DoExecLog' (line 
[--SNIP--]

What is really important is the complete log file, as pointed to by
the excerpt you quoted:

> [ERROR]    Look at '/home/jic23/x-tools/arm-at91sam7_nommu-eabi/build.log' for more info on this error.
> [ERROR]  (elapsed: 14:22.50)
> [14:30] / make: *** [build] Error 2

Compress '/home/jic23/x-tools/arm-at91sam7_nommu-eabi/build.log' with bzip2
(or lzma) and send it (if it's above ~1MiB once compressed, send it to me
privately, so as not to flood the list, please).

Without the content of that file, we can't really know what's going on.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ct-ng, arm, newlib build error
  2010-01-15 18:03 ` Yann E. MORIN
@ 2010-01-15 18:58   ` Jonathan Cameron
  2010-01-16 17:02     ` Yann E. MORIN
  0 siblings, 1 reply; 5+ messages in thread
From: Jonathan Cameron @ 2010-01-15 18:58 UTC (permalink / raw)
  To: Yann E. MORIN; +Cc: crossgcc

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

On 01/15/10 18:03, Yann E. MORIN wrote:
> Jonathan, All,
> 
> On Friday 15 January 2010 11:51:04 Jonathan Cameron wrote:
>> Has anyone seen this problem? It is occurring on one of my two machines
>> (gentoo box running pretty recent versions of everything).
> 
> And does it work on the other machine?
It builds and all looks good, but I'm getting random crashes on the board
in question that don't occur with a hand built toolchain using the same
versions of gcc newlib etc.  So something is up.  I'll take a look at 
what is different at somepoint soonish.
> 
>> This problem 
>> occured with the current mercurial tree.
> 
> I see you're using newlib-1.18.0. It's been only recently introduced, and
> I haven't had time to play with it yet.
> 
> Also, as stated in the TODO at the root of the crosstool-NG tree:
> ---8<---
> - update newlib (for enhanced bare metal)
>   - confirm existing implementation on targets other than AVR32
>   - try to make it generic, will help for uClibc++
> ---8<---
> 
> Which should be obvious that newlib support is kind of Work In Progress.
> It is currently really EXPERIMENTAL. I managed to build a newlib-based
> arm toolchain, and you should start off with it:
Sure: I'm just a perpetual optimist, and the option is very useful so I thought
I'd give it a go.  
> 
> # ct-ng show-arm-bare_newlib_cortex_m3_nommu-eabi
> arm-bare_newlib_cortex_m3_nommu-eabi  [l X]
>     OS            : bare-metal
>     GMP/MPFR      : gmp-4.3.1 / mpfr-2.4.1
>     PPL/CLOOG/MPC : ppl-0.10.2 / cloog-0.15.7 / mpc-0.7
>     binutils      : binutils-2.19.1
>     C compiler    : gcc-4.4.1 (C,C++)
>     C library     : newlib
>     Tools         :
> 
> As you already experienced, be prepared fro breakage, though...
> 
>> [ERROR]    Error happened in '/usr/local/lib/ct-ng-hg_default@1725_dbd5078816f9/scripts/functions' in function 'CT_DoExecLog' (line 
> [--SNIP--]
> 
> What is really important is the complete log file, as pointed to by
> the excerpt you quoted:
fair point, attached.  At first glance it isn't a great deal more informative.
Actually this precise log is the cvs version of newlib. Same thing at least superficially
occurs with 1.17 and 1.18 releases.
> 
>> [ERROR]    Look at '/home/jic23/x-tools/arm-at91sam7_nommu-eabi/build.log' for more info on this error.
>> [ERROR]  (elapsed: 14:22.50)
>> [14:30] / make: *** [build] Error 2

> 
> Compress '/home/jic23/x-tools/arm-at91sam7_nommu-eabi/build.log' with bzip2
> (or lzma) and send it (if it's above ~1MiB once compressed, send it to me
> privately, so as not to flood the list, please).
> 
> Without the content of that file, we can't really know what's going on.
> 
Fair point.

Thanks for the quick reply.

Jonathan

[-- Attachment #2: build.log.bz2 --]
[-- Type: application/x-bzip2, Size: 129730 bytes --]

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

--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ct-ng, arm, newlib build error
  2010-01-15 18:58   ` Jonathan Cameron
@ 2010-01-16 17:02     ` Yann E. MORIN
  2010-01-16 18:11       ` Jonathan Cameron
  0 siblings, 1 reply; 5+ messages in thread
From: Yann E. MORIN @ 2010-01-16 17:02 UTC (permalink / raw)
  To: Jonathan Cameron; +Cc: crossgcc

Jonathan, All,

On Friday 15 January 2010 19:59:51 Jonathan Cameron wrote:
> On 01/15/10 18:03, Yann E. MORIN wrote:
> > What is really important is the complete log file, as pointed to by
> > the excerpt you quoted:
> fair point, attached.  At first glance it isn't a great deal more
> informative. 
> Actually this precise log is the cvs version of newlib. Same thing at
> least superficially 
> occurs with 1.17 and 1.18 releases.

Looks very much like:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34226

And the patch attached to the PR still applies (albeit with offset):
http://gcc.gnu.org/bugzilla/attachment.cgi?id=14678&action=view

Could you please try to apply this patch to your gcc sources, try to
rebuild, and tell us the result?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: ct-ng, arm, newlib build error
  2010-01-16 17:02     ` Yann E. MORIN
@ 2010-01-16 18:11       ` Jonathan Cameron
  0 siblings, 0 replies; 5+ messages in thread
From: Jonathan Cameron @ 2010-01-16 18:11 UTC (permalink / raw)
  To: Yann E. MORIN; +Cc: crossgcc

On 01/16/10 17:02, Yann E. MORIN wrote:
> Jonathan, All,
> 
> On Friday 15 January 2010 19:59:51 Jonathan Cameron wrote:
>> On 01/15/10 18:03, Yann E. MORIN wrote:
>>> What is really important is the complete log file, as pointed to by
>>> the excerpt you quoted:
>> fair point, attached.  At first glance it isn't a great deal more
>> informative. 
>> Actually this precise log is the cvs version of newlib. Same thing at
>> least superficially 
>> occurs with 1.17 and 1.18 releases.
> 
> Looks very much like:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34226
> 
> And the patch attached to the PR still applies (albeit with offset):
> http://gcc.gnu.org/bugzilla/attachment.cgi?id=14678&action=view
> 
> Could you please try to apply this patch to your gcc sources, try to
> rebuild, and tell us the result?
> 
It does indeed look pretty similar. Unfortunately, the dumb approach
of applying that patch to gcc without really following what it is 
doing doesn't seem to fix the problem.

I haven't reattached the log as it appears to be exactly the same in the
relevant regions. (only changes are the additional local patch as per the
link above).

Thanks,

Jonathan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-01-16 18:11 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-15 10:49 ct-ng, arm, newlib build error Jonathan Cameron
2010-01-15 18:03 ` Yann E. MORIN
2010-01-15 18:58   ` Jonathan Cameron
2010-01-16 17:02     ` Yann E. MORIN
2010-01-16 18:11       ` Jonathan Cameron

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).