[SOLVED]failed build cross-toolchain for ubuntu-12.04-x86_64

Development on core packages and the distribution goes on in here.

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Sat Apr 14, 2012 4:29 pm

can builds for latest virtualbox x86_64 from my ubuntu (host) (quest = latest archlinux x86_64) its the same, identicaly problem...
http://i.imgur.com/S9Cva.png
http://i.imgur.com/v5dqO.png

hehe...quest ubuntu-11.10 x86_64 (desktop and server...all development packages)...its the same error...this build faq for cross-toolchains is fake !

http://img14.imageshack.us/img14/9513/z ... 415080.png


HOW TO BUILD THIS CROSS-TOOLCHAIN ???

(normalnie ręce i cycki opadaja...próbowałem już wszyshttp://img14.imageshack.us/img14/9 ... .pngtkiego łącznie z archbootstrap...cały czas wyskakuje ten sam błąd...co jest źle ? człowiek próbuje wszystkiego...chce się dowiedzieć konkretnie co i jak i blokada...wsparcie developerskie tego projektu zdecydowanie do czwóry...zamiast napisać prosto, jasno i po koleji ciągle Cię gdzieś odsyłają i zresztą jak wygląda na to...w ślepy zaułek...!!! :cry: )
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Mon Apr 16, 2012 2:34 am

hmmm...ok...add this patch https://bugzilla.redhat.com/show_bug.cgi?id=781765 and...cross-toolchain build from my ubuntu 12.04 x86_64...succes :D
$this->bbcode_second_pass_code('', 'slawomirj@lulo-ubuntu:~/cross/bin$ ./ct-ng build
[INFO ] Performing some trivial sanity checks
[INFO ] Build started 20120416.041202
[INFO ] Building environment variables
[EXTRA] Preparing working directories
[EXTRA] Installing user-supplied crosstool-NG configuration
[EXTRA] =================================================================
[EXTRA] Dumping internal crosstool-NG configuration
[EXTRA] Building a toolchain for:
[EXTRA] build = x86_64-unknown-linux-gnu
[EXTRA] host = x86_64-unknown-linux-gnu
[EXTRA] target = arm-unknown-linux-gnueabi
[EXTRA] Dumping internal crosstool-NG configuration: done in 0.06s (at 00:01)
[INFO ] =================================================================
[INFO ] Retrieving needed toolchain components' tarballs
[INFO ] Retrieving needed toolchain components' tarballs: done in 0.11s (at 00:01)
[INFO ] =================================================================
[INFO ] Extracting and patching toolchain components
[EXTRA] Extracting 'linux-custom'
[EXTRA] Patching 'linux-custom'
[EXTRA] Extracting 'gmp-5.0.4'
[EXTRA] Patching 'gmp-5.0.4'
[EXTRA] Extracting 'mpfr-3.1.0'
[EXTRA] Patching 'mpfr-3.1.0'
[EXTRA] Extracting 'ppl-0.11.2'
[EXTRA] Patching 'ppl-0.11.2'
[EXTRA] Extracting 'cloog-ppl-0.15.11'
[EXTRA] Patching 'cloog-ppl-0.15.11'
[EXTRA] Extracting 'mpc-0.9'
[EXTRA] Patching 'mpc-0.9'
[EXTRA] Extracting 'binutils-2.22'
[EXTRA] Patching 'binutils-2.22'
[EXTRA] Extracting 'gcc-4.6.3'
[EXTRA] Patching 'gcc-4.6.3'
[EXTRA] Extracting 'glibc-2.15'
[EXTRA] Patching 'glibc-2.15'
[EXTRA] Extracting 'glibc-ports-2.15'
[EXTRA] Patching 'glibc-ports-2.15'
[INFO ] Extracting and patching toolchain components: done in 53.72s (at 00:55)
[INFO ] =================================================================
[INFO ] Installing GMP
[EXTRA] Configuring GMP
[EXTRA] Building GMP
[EXTRA] Installing GMP
[INFO ] Installing GMP: done in 26.57s (at 01:21)
[INFO ] =================================================================
[INFO ] Installing MPFR
[EXTRA] Configuring MPFR
[EXTRA] Building MPFR
[EXTRA] Installing MPFR
[INFO ] Installing MPFR: done in 12.64s (at 01:34)
[INFO ] =================================================================
[INFO ] Installing PPL
[EXTRA] Configuring PPL
[EXTRA] Building PPL
[EXTRA] Installing PPL
[INFO ] Installing PPL: done in 95.65s (at 03:10)
[INFO ] =================================================================
[INFO ] Installing CLooG/ppl
[EXTRA] Configuring CLooG/ppl
[EXTRA] Building CLooG/ppl
[EXTRA] Installing CLooG/ppl
[INFO ] Installing CLooG/ppl: done in 4.57s (at 03:14)
[INFO ] =================================================================
[INFO ] Installing MPC
[EXTRA] Configuring MPC
[EXTRA] Building MPC
[EXTRA] Installing MPC
[INFO ] Installing MPC: done in 5.49s (at 03:20)
[INFO ] =================================================================
[INFO ] Installing binutils
[EXTRA] Configuring binutils
[EXTRA] Building binutils
[EXTRA] Installing binutils
[INFO ] Installing binutils: done in 28.07s (at 03:48)
[INFO ] =================================================================
[INFO ] Installing static core C compiler
[EXTRA] Configuring static core C compiler
[EXTRA] Building static core C compiler
[EXTRA] Installing static core C compiler
[INFO ] Installing static core C compiler: done in 90.62s (at 05:18)
[INFO ] =================================================================
[INFO ] Installing kernel headers
[EXTRA] Installing kernel headers
[EXTRA] Checking installed headers
[INFO ] Installing kernel headers: done in 3.27s (at 05:22)
[INFO ] =================================================================
[INFO ] Installing C library headers & start files
[EXTRA] Configuring C library
[EXTRA] Installing C library headers
[EXTRA] Installing C library start files
[INFO ] Installing C library headers & start files: done in 33.32s (at 05:55)
[INFO ] =================================================================
[INFO ] Installing shared core C compiler
[EXTRA] Configuring shared core C compiler
[EXTRA] Building shared core C compiler
[EXTRA] Installing shared core C compiler
[INFO ] Installing shared core C compiler: done in 123.36s (at 07:58)
[INFO ] =================================================================
[INFO ] Installing C library
[EXTRA] Configuring C library
[EXTRA] Building C library
[EXTRA] Installing C library
[INFO ] Installing C library: done in 367.27s (at 14:06)
[INFO ] =================================================================
[INFO ] Installing final compiler
[EXTRA] Configuring final compiler
[EXTRA] Building final compiler
[EXTRA] Installing final compiler
[INFO ] Installing final compiler: done in 158.05s (at 16:44)
[INFO ] =================================================================
[INFO ] Cleaning-up the toolchain's directory
[INFO ] Stripping all toolchain executables
[EXTRA] Installing the populate helper
[EXTRA] Installing a cross-ldd helper
[EXTRA] Creating toolchain aliases
[EXTRA] Removing access to the build system tools
[EXTRA] Removing installed documentation
[INFO ] Cleaning-up the toolchain's directory: done in 0.98s (at 16:45)
[INFO ] Build completed at 20120416.042847
[INFO ] (elapsed: 16:44.72)
[INFO ] Finishing installation (may take a few seconds)...
[16:45] / slawomirj@lulo-ubuntu:~/cross/bin$
')

important question: its like using this patch for builds cross-toolchain => distcc working and build properly from archlinuxarm (alarm for iconnect) ?
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Mon Apr 16, 2012 3:51 am

ehhh...not working properly and not build..anything

$this->bbcode_second_pass_code('', '
...
...
...
distcc[23347] ERROR: compile dialogs.c on 192.168.1.202 failed
distcc[23347] (dcc_build_somewhere) Warning: remote compilation of 'dialogs.c' failed, retrying locally
distcc[23347] Warning: failed to distribute dialogs.c to 192.168.1.202, running locally instead
distcc[23347] (dcc_please_send_email_after_investigation) Warning: remote compilation of 'dialogs.c' failed, retried locally and got a different result.
...
...
...
')

:cry:
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby Philoo » Mon Apr 16, 2012 2:36 pm

$this->bbcode_second_pass_quote('lulo', '
')important question: its like using this patch for builds cross-toolchain => distcc working and build properly from archlinuxarm (alarm for iconnect) ?


hmm the iconnect is armv5, so if you are running arch on it and want to dist-compile for another armv5 system, you do not need the crosstool. Just have the base-devel package installed and follow the dist-cc tuto.

As for v7h target this is most likely "just" a matter of CCFLAGS, so no need for cross tools. I've not experimented with v7h yet so do not take my word for it.

please note that I would not use the iconnect as a dist compile slave if it runs from a thumb drive as this will kill the thumb drive in no time. (hard drive enclosure and/or network mounted share should be fine if not the fastest)
Philoo
 
Posts: 102
Joined: Wed Aug 10, 2011 9:20 pm

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Tue Apr 17, 2012 11:59 am

$this->bbcode_second_pass_quote('Philoo', '
')hmm the iconnect is armv5, so if you are running arch on it and want to dist-compile for another armv5 system, you do not need the crosstool...

I'm dont wont to dist-compile for another armv5 system...I'm wont to dist -compile for ubuntu-12.04 x86_64 or another linux => I'am need the crosstool...right ?
$this->bbcode_second_pass_quote('Philo', '
')please note that I would not use the iconnect as a dist compile slave if it runs from a thumb drive as this will kill the thumb drive in no time. (hard drive enclosure and/or network mounted share should be fine if not the fastest)


uses iconnect as a dist compile "master"...runs this system arch-armv5 from hard drive (many GiB + swap file = ~ 1 GiB)...not a thumb drive..."slave" is would fastest and strong machine...eg. PC computer x86_64...many cores, ram, etc....right ? => the crosstool is needed...right ?
;)

general: I'am need toolchain...i'am need dist compile (alarm + many other packages = extra, community, core, custom...custom....custom...) from another linux x86_64 ... ( something like openwrt-toolchain from other linux x86_64, other distributions linux from different distribution linux, etc.)
:D :D :D :D
HOW ???
not a the crosstool ?
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am
Top

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Wed Jun 13, 2012 1:33 pm

new/actual instruction (new crosstool-ng)...is the same bug:
$this->bbcode_second_pass_code('', '[INFO ] Installing C library
[EXTRA] Configuring C library
[EXTRA] Building C library
[ERROR] collect2: error: ld returned 1 exit status
[ERROR] make[3]: *** [/home/lulojs/cross/bin/.build/arm-unknown-linux-gnueabi/build/build-libc-final/malloc/libmemusage.so] Error 1
[ERROR] make[2]: *** [malloc/others] Error 2
[ERROR] make[1]: *** [all] Error 2
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing C library'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@172]
[ERROR] >> called from: do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@441]
[ERROR] >> called from: do_libc_backend[scripts/build/libc/glibc-eglibc.sh-common@143]
[ERROR] >> called from: do_libc[scripts/build/libc/glibc-eglibc.sh-common@65]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@598]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> '/home/lulojs/cross/share/doc/crosstool-ng/ct-ng.1.15.2/B - Known issues.txt'
[ERROR]
[ERROR] (elapsed: 13:30.83)
[13:31] / make: *** [build] Błąd 2')

actual build for ubuntu precise x86_64.

instruction http://archlinuxarm.org/developers/dist ... -compiling:
$this->bbcode_second_pass_quote('', '.')..Pre-built crosstool-ng toolchains
In lieu of building the toolchain as detailed below, if you are running a 64-bit Linux installation you can try to use these packaged toolchains that are employed in the official build system:

ARMv5te soft (8799ccfbfdc418ff68c8a5a3996718fe) ...


http://archlinuxarm.org/buider/xtools/x-tools.tar.xz link is dead...no file for this url...
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am
Top

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby WarheadsSE » Wed Jun 13, 2012 1:51 pm

Dangit. Typo. Fixed on the page now.
http://archlinuxarm.org/builder/xtools/x-tools.tar.xz
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Wed Jun 13, 2012 3:00 pm

for instruction http://archlinuxarm.org/developers/dist ... -compiling :

$this->bbcode_second_pass_quote('', '.')..
Make nice with distcc
The toolchain will install under "~/x-tools" for armv5 and "~/x-tools7h" for armv7 hard-float. You can move this somewhere else if you like, or leave it where it is. Before we can use the compiler binaries that were created, links need to be created to make their names more appropriate. When compile jobs are sent to distcc, the program specified in the CC environment variable on the build master is what gets executed on the build clients. All the binaries that have been produced by crosstool-ng are in the correct format specifying the target platform as a prefix, though not with the correct platform and lacking tuple-less variants. This script will fix our problem. Make "~/x-tools/arm-unknown-linux-gnueabi/bin/" writable and in there create a file called "link" and paste this into it. Run it afterward.

#!/bin/bash
for file in `ls`; do
if [[ "$file" == "link" ]]; then
continue
fi
ln -s $file ${file#arm-unknown-linux-gnueabi-}
# uncomment for v7
# ln -s $file armv7l-unknown-linux-gnueabi-${file#arm-unknown-linux-gnueabi-}
done
...


script "link" not produce this symlink for ~/x-tools/arm-unknown-linux-gnueabi/bin :
armv5tel-unknown-linux-gnueabi-addr2line,armv5tel*ar,armv5tel*as, ...etc

this is important or not from build/compiling can use distcc ?
Last edited by lulo on Wed Jun 13, 2012 11:33 pm, edited 1 time in total.
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am
Top

Re: failed build cross-toolchain for ubuntu-12.04-x86_64-bet

Postby lulo » Wed Jun 13, 2012 5:34 pm

SUKCES ! SUKCES ! SUKCES !
build for my ubuntu precise crosstool-ng from instruction (for glibc-port use this patch https://bugzilla.redhat.com/show_bug.cgi?id=781765 - fix build x-tools => fix libmemusage.so for my processor AMD FX-8150)
add this lost symlink and...everyting build ok (eg. previous lintorrent) - fragment log for /var/log/distccd.log (ubuntu precise x86_64) :

$this->bbcode_second_pass_code('', 'distccd[16778] (dcc_job_summary) client: 192.168.1.248:43353 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3611ms g++ block_list.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43354 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4769ms g++ chunk_utils.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43352 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5946ms g++ block.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43355 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2061ms g++ file.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43357 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2540ms g++ file_list_iterator.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43358 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2636ms g++ file_manager.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43356 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5121ms g++ file_list.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43359 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1755ms g++ file_utils.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43360 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2618ms g++ transfer_list.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43363 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5333ms g++ download_manager.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43362 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5667ms g++ choke_group.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43361 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6281ms g++ choke_queue.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43364 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2821ms g++ resource_manager.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43365 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1654ms g++ client_info.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43366 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4094ms g++ client_list.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43367 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6659ms g++ connection_list.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43368 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4171ms g++ peer.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43369 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3196ms g++ peer_info.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43370 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2343ms g++ peer_list.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43372 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4294ms g++ option_strings.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43371 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5110ms g++ log_files.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43373 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:9353ms g++ resume.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43375 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2868ms g++ bitfield.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43376 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3413ms g++ chunk_manager.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43374 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3480ms g++ connection_manager.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43379 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1586ms g++ error.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43377 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5127ms g++ dht_manager.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43380 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2023ms g++ exceptions.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43378 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6136ms g++ download.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43381 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2288ms g++ hash_string.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43382 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2699ms g++ http.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43384 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2751ms g++ object_static_map.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43386 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1380ms g++ path.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43383 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7605ms g++ object.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43387 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1335ms g++ poll_epoll.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43385 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7411ms g++ object_stream.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43388 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2086ms g++ poll_kqueue.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43389 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2975ms g++ poll_select.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43391 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1342ms g++ thread_base.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43390 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3046ms g++ rate.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43392 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3323ms g++ throttle.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43394 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2086ms g++ tracker.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43393 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5608ms g++ torrent.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43395 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2757ms g++ tracker_list.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43396 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2968ms g++ chunk_part.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43398 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3499ms g++ chunk.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43397 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4457ms g++ chunk_list.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43399 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2587ms g++ hash_chunk.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43401 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2746ms g++ hash_queue_node.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43400 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4397ms g++ hash_queue.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43402 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2971ms g++ hash_torrent.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43403 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2215ms g++ memory_chunk.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43404 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1971ms g++ socket_file.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43405 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4278ms g++ dht_bucket.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43407 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7124ms g++ dht_node.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43409 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1778ms g++ dht_tracker.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43406 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:9644ms g++ dht_router.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43408 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6264ms g++ dht_server.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43410 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2075ms g++ dht_transaction.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43412 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3159ms g++ chunk_statistics.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43413 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3755ms g++ chunk_selector.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43411 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4209ms g++ available_list.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43414 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3246ms g++ delegator.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43416 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7583ms g++ download_main.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43417 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5784ms g++ download_wrapper.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43415 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:9901ms g++ download_constructor.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43420 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3418ms g++ socket_base.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43418 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3909ms g++ listen.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43419 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5349ms g++ address_list.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43421 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1974ms g++ socket_datagram.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43422 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2519ms g++ socket_fd.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43423 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3190ms g++ socket_set.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43424 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2702ms g++ socket_stream.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43425 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3090ms g++ throttle_internal.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43426 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1570ms g++ throttle_list.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43427 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4181ms g++ handshake_encryption.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43428 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7405ms g++ extensions.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43429 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7387ms g++ handshake.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43430 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3175ms g++ handshake_manager.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43431 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5675ms g++ initial_seed.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43432 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7418ms g++ peer_connection_base.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43433 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:8335ms g++ peer_connection_leech.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43434 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3814ms g++ peer_connection_metadata.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43435 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2301ms g++ peer_factory.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43436 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2003ms g++ request_list.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43438 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5493ms g++ tracker_dht.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43439 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5917ms g++ tracker_manager.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43437 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7107ms g++ tracker_http.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43440 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:3418ms g++ tracker_udp.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43441 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:897ms g++ sha_fast.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43442 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1567ms g++ diffie_hellman.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43444 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2077ms g++ globals.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43443 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4219ms g++ manager.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43445 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:367ms cc /tmp/cgeXmcLQ/dummy.c
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43446 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4904ms g++ curl_socket.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43447 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:5371ms g++ curl_get.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43448 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6286ms g++ curl_stack.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43450 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:8818ms g++ download.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43449 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:10045ms g++ dht_manager.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43451 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:10726ms g++ download_factory.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43454 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2856ms g++ http_queue.cc
distccd[16799] (dcc_job_summary) client: 192.168.1.248:43455 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:2048ms g++ log.cc
distccd[16781] (dcc_job_summary) client: 192.168.1.248:43453 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:7797ms g++ download_store.cc
distccd[16778] (dcc_job_summary) client: 192.168.1.248:43452 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:8972ms g++ download_list.cc
distccd[16800] (dcc_job_summary) client: 192.168.1.248:43458 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4337ms g++ poll_manager_epoll.cc
distccd[16801] (dcc_job_summary) client: 192.168.1.248:43457 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4977ms g++ poll_manager.cc
distccd[16784] (dcc_job_summary) client: 192.168.1.248:43456 COMPILE_ERROR exit:1 sig:0 core:0 ret:0 time:5638ms g++ manager.cc
distccd[16783] (dcc_job_summary) client: 192.168.1.248:43459 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4336ms g++ poll_manager_kqueue.cc
distccd[16802] (dcc_job_summary) client: 192.168.1.248:43460 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:4529ms g++ poll_manager_select.cc
distccd[16782] (dcc_job_summary) client: 192.168.1.248:43462 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:6584ms g++ view_manager.cc
distccd[16798] (dcc_job_summary) client: 192.168.1.248:43461 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:10420ms g++ view.cc')

my iomega (makepkg --asroot; not add this time normal user) producet finally and not errors (manualy installed and tested - it is worging ok) modified package libtorrent-0.12.9-1.with_pre_allocate-arm.pkg.tar.xz for my old rtorrent-0.8.9...very nice !

at lenght !!!

:D :D :D
lulo
 
Posts: 90
Joined: Mon Nov 28, 2011 1:19 am

Re: [SOLVED]failed build cross-toolchain for ubuntu-12.04-x8

Postby d3xtro » Fri Jun 29, 2012 7:26 am

I have followed everything on http://archlinuxarm.org/developers/dist ... -compiling and http://archlinuxarm.org/developers/dist ... -compiling but keep getting $this->bbcode_second_pass_code('', 'distcc[24299] (dcc_build_somewhere) Warning: failed to distribute, running locally instead')distcc doesn't seem to have log files on either end so I can't even look into why! :(

Edit: also getting $this->bbcode_second_pass_code('', 'distcc[28531] (dcc_writex) ERROR: failed to write: Connection reset by peer') now that I added $this->bbcode_second_pass_code('', ' /home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/cc
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/c++
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/c89
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/c99
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/gcc
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/g++
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/*gcc-*
/home/notroot/x-tools-new/arm-unknown-linux-gnueabi/bin/*g++-*
') to allowed_compilers in /etc/distcc/commands.allow.sh
d3xtro
 
Posts: 13
Joined: Wed Mar 21, 2012 6:55 am

PreviousNext

Return to Arch Linux ARM

Who is online

Users browsing this forum: No registered users and 9 guests