mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Martin Breidung <titus@complab.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Not reproducable bugs on compiling OSELAS Toolchain
Date: Thu, 23 Feb 2012 13:39:17 +0100	[thread overview]
Message-ID: <B09C6618-D997-4624-A986-4FC592BD742C@complab.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4778 bytes --]

I got errors on compiling the toolchain OSELAS.Toolchain-2011.11.1.

System: Ubuntu 11.10

On Ubuntu 10.4 LTS i got errors too withe OSELAS.Toolchain-2011.11.0.

Ubuntu is running under VMware Fusion on a MacBookPro i7 Early 2011.


Which OS is recommended for compiling the toolchain or what can I do to make it work?


echo CRTSTUFF_CFLAGS = '-O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -I. -I. -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc/. -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc/../include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc/../libcpp/include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/sysroot-host/include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/sysroot-host/include  -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc/../libdecnumber -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.11.1/platform-arm-v4t-linux-gnueabi-gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/build-cross/gcc-4.6.2/gcc/../libdecnumber/dpd -I../libdecnumber    -g0 -finhibit-size-directive -fno-inline -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-tree-vectorize -fno-stack-protector ' >> tmp-libgcc.mvars
echo CRTSTUFF_T_CFLAGS = '' >> tmp-libgcc.mvars
echo CRTSTUFF_T_CFLAGS_S = ' -fPIC' >> tmp-libgcc.mvars
echo TARGET_SYSTEM_ROOT = '/opt/OSELAS.Toolchain-2011.11.1/arm-v4t-linux-gnueabi/gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/sysroot-arm-v4t-linux-gnueabi' >> tmp-libgcc.mvars
mv tmp-libgcc.mvars libgcc.mvars
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [lto/lto-lang.o] Error 1


Similar problem with OSELAS.Toolchain-2011.03.1:

gcc -c  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat   -DHAVE_CONFIG_H -I. -I. -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/. -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/../include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/../libcpp/include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/sysroot-host/include -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/sysroot-host/include  -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/../libdecnumber -I/home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/../libdecnumber/dpd -I../libdecnumber   -I/usr/include/libelf  /home/titus/_workspace.ptx/OSELAS.Toolchain-2011.03.1/platform-arm-v4t-linux-gnueabi-gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/build-cross/gcc-4.5.2/gcc/rtlhooks.c -o rtlhooks.o
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [omp-low.o] Error 1


[-- Attachment #1.2: Type: text/html, Size: 6157 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2012-02-23 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 12:39 Martin Breidung [this message]
2012-02-23 13:01 ` Alexander Dahl
2012-02-24 18:48   ` Martin Breidung
2012-02-25  0:31   ` [ptxdist] [SOLVED] " Martin Breidung
2012-02-23 13:43 ` [ptxdist] " Andreas Bießmann
2012-02-24 18:51   ` Martin Breidung
2012-02-25  8:21     ` Andreas Bießmann
2012-02-26 17:55       ` Bernhard Walle

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=B09C6618-D997-4624-A986-4FC592BD742C@complab.de \
    --to=titus@complab.de \
    --cc=ptxdist@pengutronix.de \
    /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