Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] GIT or SVN
Date: Thu, 19 Jun 2008 12:53:51 +0200	[thread overview]
Message-ID: <485A3ABF.90707@cetrtapot.si> (raw)
In-Reply-To: <485A3396.80701@cetrtapot.si>

Hinko Kocevar wrote:
> Hello,
> 
> I'm new to the uclibc buildroot. I've noticed that there are two repositories: GIT and SVN. GIT looks more up2date. Is GIT the tree to use?
> 
> Also, I'm trying to create a uclibc toolchain for cris architecture. 

And here is the 1st problem with cris toolchain. When building gcc-final libgomp wants threads... The gcc was configured with threads enabled and BR2 has BR2_PTHREADS_OLD=y. Here is gcc configure line:
$ /work/stage/buildroot/toolchain_build_cris/gcc-4.3.0/configure --prefix=/usr --build=i386-pc-linux-gnu --host=i386-pc-linux-gnu --target=cris-linux-uclibc --enable-languages=c --with-sysroot=/work/stage/buildroot/build_cris/staging_dir --with-build-time-tools=/work/stage/buildroot/build_cris/staging_dir/usr/cris-linux-uclibc/bin --disable-__cxa_atexit --enable-target-optspace --with-gnu-ld --disable-shared --with-gmp=/work/stage/buildroot/toolchain_build_cris/gmp --with-mpfr=/work/stage/buildroot/toolchain_build_cris/mpfr --disable-nls --enable-threads --disable-multilib --disable-largefile

FAILURE:

...
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
libtool.m4: error: problem compiling FC test program
checking for cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include option to produce PIC... -fPIC
checking if cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include PIC flag -fPIC works... no
checking if cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include static flag -static works... no
checking if cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include supports -c -o file.o... no
checking if cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include supports -c -o file.o... (cached) no
checking whether the cris-linux-uclibc-gfortran -B/usr/cris-linux-uclibc/bin/ -B/usr/cris-linux-uclibc/lib/ -isystem /usr/cris-linux-uclibc/include -isystem /usr/cris-linux-uclibc/sys-include linker (/work/stage/buildroot/toolchain_build_cris/gcc-4.3.0-final/./gcc/collect-ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking for unistd.h... (cached) yes
checking semaphore.h usability... yes
checking semaphore.h presence... yes
checking for semaphore.h... yes
checking sys/loadavg.h usability... no
checking sys/loadavg.h presence... no
checking for sys/loadavg.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
looking for a compliant stdint.h in stdint.h, checking for uintmax_t... yes
checking for uintptr_t... yes
checking for int_least32_t... yes
checking for int_fast32_t... yes
checking for uint64_t... yes
checking what to include in gstdint.h... stdint.h (already complete)
configure: error: Pthreads are required to build libgomp
make[2]: *** [configure-target-libgomp] Error 1
make[2]: Leaving directory `/work/stage/buildroot/toolchain_build_cris/gcc-4.3.0-final'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/work/stage/buildroot/toolchain_build_cris/gcc-4.3.0-final'
make: *** [/work/stage/buildroot/toolchain_build_cris/gcc-4.3.0-final/.compiled] Error 2


I'll try older gcc version to see if the error persists.

Regards,
Hinko

-- 
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si

  reply	other threads:[~2008-06-19 10:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 10:23 [Buildroot] GIT or SVN Hinko Kocevar
2008-06-19 10:53 ` Hinko Kocevar [this message]
2008-06-19 11:13   ` Bernhard Fischer
2008-06-19 11:54     ` Hinko Kocevar
2008-06-19 12:03       ` Bernhard Fischer
2008-06-19 12:20         ` Hinko Kocevar
2008-06-19 13:25         ` Hinko Kocevar
2008-06-19 19:09 ` Peter Korsgaard
2008-06-20  8:36   ` Bernhard Fischer
2008-06-20  8:40     ` Hinko Kocevar
2008-06-20 12:57       ` Bernhard Fischer
2008-06-20 13:15         ` Hinko Kocevar
2008-06-20 13:24           ` Bernhard Fischer
2008-06-23 10:10             ` Hinko Kocevar
2008-06-20 13:26         ` Hinko Kocevar
2008-06-20 14:11           ` [Buildroot] cris Bernhard Fischer
2008-06-20 14:30             ` Peter Korsgaard
2008-06-20 15:03               ` Bernhard Fischer
2008-06-23  7:27             ` Hinko Kocevar
2008-06-23  8:50               ` Hinko Kocevar
2008-06-23 13:06                 ` Bernhard Fischer
2008-06-23 14:48                   ` Hinko Kocevar
2008-06-23 13:03               ` Bernhard Fischer
2008-06-23 14:41                 ` Hinko Kocevar
2008-06-23 14:46                   ` Bernhard Fischer
2008-06-23 14:54                     ` Hinko Kocevar
2008-06-23 15:01                       ` Bernhard Fischer
2008-07-30  2:39                       ` Ralph Siemsen
2008-06-20 13:18       ` [Buildroot] GIT or SVN Peter Korsgaard
2008-07-30  8:20         ` Hinko Kocevar

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=485A3ABF.90707@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --cc=buildroot@busybox.net \
    /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