Thanks a lot, it builds now fine!!

regards,

Ingmar

René Rebe wrote:
> Hi,
> 
> ah thanks.
> 
> Committed revision 32652.
> 
> Have fun,
>  René
> 
> Ingmar Schraub wrote:
>> Here you go.
>>
>> Thanks, Ingmar
>>
>> René Rebe wrote:
>>  
>>> Yes, it helped, so it's csh (though we patch that away already,
>>> strange).
>>>
>>> Can you also send me the build/.../var/adm/logs/1-groff.err?
>>>
>>> Ingmar Schraub wrote:
>>>    
>>>> Please find it attached. I hope it helps.
>>>>
>>>> cheers, Ingmar
>>>>
>>>> René Rebe wrote:
>>>>  
>>>>      
>>>>> Can you send me the write log file of the failed groff build:
>>>>>
>>>>> src.groff. ... fl_wrapper.wlog
>>>>>
>>>>> to get an idea what program created the /root/.history?
>>>>>
>>>>> Ingmar Schraub wrote:
>>>>>           
>>>>>> Thanks a lot. I had disabled that package for now and the build is
>>>>>> continuing.
>>>>>>
>>>>>> I noticed also that 'popt' wants 'gettext' first, but it wasn't built
>>>>>> first. So I built it manually with ./scripts/Build-Pkg gettext and
>>>>>> ran
>>>>>> ./scripts/Build-Target again. That worked.
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Ingmar
>>>>>>
>>>>>> René Rebe wrote:
>>>>>>  
>>>>>>               
>>>>>>> Hi again,
>>>>>>>
>>>>>>> René Rebe wrote:
>>>>>>>                      
>>>>>>>> I think I do not see the offending file in the shortened log,
>>>>>>>>                               
>>>>>>> Heh it's the .history, I only looked at the #base lines:
>>>>>>>
>>>>>>> !> Created file outside basedir: /root/.history
>>>>>>> !> base #1: /home/ingmar/dev/t2-trunk
>>>>>>> !> base #2:
>>>>>>> /home/ingmar/dev/t2-trunk/build/default-8.0-trunk-generic-x86-64
>>>>>>>
>>>>>>> I'll take a look, now :-)
>>>>>>>
>>>>>>>                      
>>>>>>>> but I guess some tch or so history file in the /root directory?
>>>>>>>>
>>>>>>>> I saw this recently, too but was too lazy to patch the configure
>>>>>>>> script immediatly.
>>>>>>>>
>>>>>>>> Can take a look in some other minute.
>>>>>>>>
>>>>>>>> Ingmar Schraub wrote:
>>>>>>>>                            
>>>>>>>>> Hi René,
>>>>>>>>>
>>>>>>>>> that's a very fast fix! Impressive!! I tried and it worked just
>>>>>>>>> fine.
>>>>>>>>> Unfortunately I ran into the next issue:
>>>>>>>>>
>>>>>>>>> groff fails with
>>>>>>>>>
>>>>>>>>> == 16:39:31 =[1]=> Building archiver/tar [1.22 8.0-trunk].
>>>>>>>>> -> Parallel build using 2 jobs enabled.
>>>>>>>>> -> Reading package config: package/archiver/tar/tar.conf
>>>>>>>>> -> Preparing build in src.tar.default.20090318.163930.25665.nexoc
>>>>>>>>> -> Building. Writing output to $root/var/adm/logs/1-tar.out
>>>>>>>>> -> $root/var/adm/logs/1-tar.out -> 1-tar.log
>>>>>>>>> == 03/18/09 16:40:46 =[1]=> Finished building package tar.
>>>>>>>>>
>>>>>>>>> == 16:40:47 =[1]=> Building base/groff [1.20.1 8.0-trunk].
>>>>>>>>> -> Reading package config: package/base/groff/groff.conf
>>>>>>>>> -> Preparing build in src.groff.default.20090318.164046.8468.nexoc
>>>>>>>>> -> Building. Writing output to $root/var/adm/logs/1-groff.out
>>>>>>>>> !> ==[build_this_package:992 (last $?=0)> '[' '
>>>>>>>>> /home/ingmar/dev/t2-trunk/build/default-8.0-trunk-generic-x86-64/usr/doc/groff'
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ']'
>>>>>>>>> !> ==[build_this_package:993 (last $?=0)> rmdir
>>>>>>>>> /home/ingmar/dev/t2-trunk/build/default-8.0-trunk-generic-x86-64/usr/doc/groff
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> !> ==[build_this_package:996 (last $?=0)> return 0
>>>>>>>>> !> =[:609 (last $?=0)> set +o xtrace
>>>>>>>>> !> Creating file list and doing final adaptions ...
>>>>>>>>> !> Created file outside basedir: /root/.history
>>>>>>>>> !> base #1: /home/ingmar/dev/t2-trunk
>>>>>>>>> !> base #2:
>>>>>>>>> /home/ingmar/dev/t2-trunk/build/default-8.0-trunk-generic-x86-64
>>>>>>>>> !> removed
>>>>>>>>> `/home/ingmar/dev/t2-trunk/build/default-8.0-trunk-generic-x86-64/var/adm/logs/1-groff.log'
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -> $root/var/adm/logs/1-groff.out -> 1-groff.err
>>>>>>>>> == 03/18/09 16:42:17 =[1]=> Aborted building package groff.
>>>>>>>>>
>>>>>>>>> What's wrong here?
>>>>>>>>>
>>>>>>>>> regards,
>>>>>>>>>
>>>>>>>>> Ingmar
>>>>>>>>>
>>>>>>>>> René Rebe wrote:
>>>>>>>>>  
>>>>>>>>>                                  
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Committed revision 32648.
>>>>>>>>>>
>>>>>>>>>> Yours,
>>>>>>>>>>
>>>>>>>>>> Ingmar Schraub wrote:
>>>>>>>>>>                                          
>>>>>>>>>>> Thanks a lot René!
>>>>>>>>>>>
>>>>>>>>>>> Apparently I had overlooked the 'contact' section on your
>>>>>>>>>>> website.
>>>>>>>>>>> Sorry
>>>>>>>>>>> for that.
>>>>>>>>>>>
>>>>>>>>>>> My trunk checkout is 'current'
>>>>>>>>>>>
>>>>>>>>>>> Path: .
>>>>>>>>>>> URL: http://svn.exactcode.de/t2/trunk
>>>>>>>>>>> Repository Root: http://svn.exactcode.de/t2
>>>>>>>>>>> Repository UUID: c5f82cb5-29bc-0310-9cd0-bff59a50e3bc
>>>>>>>>>>> Revision: 32647
>>>>>>>>>>> Node Kind: directory
>>>>>>>>>>> Schedule: normal
>>>>>>>>>>> Last Changed Author: rene
>>>>>>>>>>> Last Changed Rev: 32647
>>>>>>>>>>> Last Changed Date: 2009-03-18 15:55:58 +0100 (Wed, 18 Mar 2009)
>>>>>>>>>>>
>>>>>>>>>>> tar does not build with my settings (target x86_64, glibc).
>>>>>>>>>>>
>>>>>>>>>>> Here we go again:
>>>>>>>>>>> Found 7 new/updated files in source tree:
>>>>>>>>>>> -> Found new/updated file:
>>>>>>>>>>> package/gnome2/gnome-python/gnome-python.desc
>>>>>>>>>>> -> Found new/updated file:
>>>>>>>>>>> package/gnome2/gnome-nettool/gnome-nettool.desc
>>>>>>>>>>> -> Found new/updated file: package/gnome2/librsvg/librsvg.desc
>>>>>>>>>>> -> ** list truncated to save space on the terminal **
>>>>>>>>>>>
>>>>>>>>>>> Re-running configuration:
>>>>>>>>>>> -> Aquiring config write lock (may take until other configs
>>>>>>>>>>> finished) ...
>>>>>>>>>>> -> T2 8.0-trunk configuration ...
>>>>>>>>>>> -> Building src/luabash.so.
>>>>>>>>>>> -> INSTALL DYNLIB
>>>>>>>>>>> /home/ingmar/dev/t2-trunk/src/Linux-x86_64/bash/luabash.so
>>>>>>>>>>> -> LUA accelerator (C) 2006 by Valentin Ziegler & Rene Rebe,
>>>>>>>>>>> ExactCODE
>>>>>>>>>>> -> New config written to config/default/*.
>>>>>>>>>>> -> Cleaning up. Configuration finished.
>>>>>>>>>>>
>>>>>>>>>>> Building tools in build/.../TOOLCHAIN/tools.cross:
>>>>>>>>>>> -> Building tools.cross/wrapper/cmd_wrapper.
>>>>>>>>>>> -> Building tools.cross/wrapper/strip_wrapper.
>>>>>>>>>>> -> Building tools.cross/wrapper/{uname,arch}.
>>>>>>>>>>> -> Building tools.cross/wrapper/install_wrapper.
>>>>>>>>>>> -> Building tools.cross/bin/getdu.
>>>>>>>>>>> -> Building tools.cross/bin/getfiles.
>>>>>>>>>>> -> Building tools.cross/bin/fl_wrparse.
>>>>>>>>>>> -> Building tools.cross/bin/fl_stparse.
>>>>>>>>>>> -> Building tools.cross/lib/fl_wrapper.so.
>>>>>>>>>>> -> Testing tools.cross/lib/fl_wrapper.so.
>>>>>>>>>>> -> Creating tools.cross/lib/parse-config.
>>>>>>>>>>> -> Creating tools.cross/lib/pkg_*_{pre,post}.conf
>>>>>>>>>>>
>>>>>>>>>>> Removing old error logs ...
>>>>>>>>>>> -> Removing var/adm/logs/1-tar.err ...
>>>>>>>>>>>
>>>>>>>>>>> == 16:15:10 =[1]=> Building archiver/tar [1.22 8.0-trunk].
>>>>>>>>>>> -> Parallel build using 2 jobs enabled.
>>>>>>>>>>> -> Reading package config: package/archiver/tar/tar.conf
>>>>>>>>>>> -> Preparing build in src.tar.default.20090318.161509.1096.nexoc
>>>>>>>>>>> -> Building. Writing output to $root/var/adm/logs/1-tar.out
>>>>>>>>>>> !> checking whether program_invocation_name is declared... yes
>>>>>>>>>>> !> checking whether program_invocation_short_name is
>>>>>>>>>>> declared... yes
>>>>>>>>>>> !> checking whether program_invocation_name is defined... yes
>>>>>>>>>>> !> checking whether program_invocation_short_name is defined...
>>>>>>>>>>> yes
>>>>>>>>>>> !> checking whether btowc(EOF) is correct... configure: error:
>>>>>>>>>>> cannot
>>>>>>>>>>> run test program while cross compiling
>>>>>>>>>>> !> See `config.log' for more details.
>>>>>>>>>>> !> Due to previous errors, no 1-tar.log file!
>>>>>>>>>>> !> (Try enabling xtrace in the config to track an error
>>>>>>>>>>> inside the
>>>>>>>>>>> build
>>>>>>>>>>> system.)
>>>>>>>>>>> -> $root/var/adm/logs/1-tar.out -> 1-tar.err
>>>>>>>>>>> == 03/18/09 16:15:49 =[1]=> Aborted building package tar.
>>>>>>>>>>> -> Unmounting loop mounts ...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Do you have any ideas/pointers?
>>>>>>>>>>>
>>>>>>>>>>> Thanks and kind regards,
>>>>>>>>>>>
>>>>>>>>>>> Ingmar
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> René Rebe wrote:
>>>>>>>>>>>  
>>>>>>>>>>>                                                  
>>>>>>>>>>>> Dear Ingmar,
>>>>>>>>>>>>
>>>>>>>>>>>> welcome in the T2 world.
>>>>>>>>>>>>
>>>>>>>>>>>>  http://t2-project.org/contact/
>>>>>>>>>>>>
>>>>>>>>>>>> Please try to post to the list in the future, as it potentially
>>>>>>>>>>>> allows other people to comment as well (and I already
>>>>>>>>>>>> nearly forgot about the mail in my populated inbox).
>>>>>>>>>>>>
>>>>>>>>>>>> How old is your trunk checkout (svn info)? A quick
>>>>>>>>>>>> test build looks good for ARM / uclibc:
>>>>>>>>>>>>
>>>>>>>>>>>> == 03/18/09 16:15:16 =[1]=> Finished building package tar.
>>>>>>>>>>>>
>>>>>>>>>>>> Ingmar Schraub wrote:
>>>>>>>>>>>>                                                             
>>>>>>>>>>>>> Hallo,
>>>>>>>>>>>>>
>>>>>>>>>>>>> ich habe gestern meinen ersten Versuch mit t2 gestartet.
>>>>>>>>>>>>> Bislang
>>>>>>>>>>>>> habe
>>>>>>>>>>>>> ich viel mit buildroot/uClibc gearbeitet.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nun bin ich auf ein Problem gestossen und weiss hier leider
>>>>>>>>>>>>> (als
>>>>>>>>>>>>> Neuling) nicht weiter. Das package 'tar' lässt sich nicht
>>>>>>>>>>>>> übersetzen.
>>>>>>>>>>>>> S.u.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Als Target habe ich x86_64 mit glibc gewählt. Als build-host
>>>>>>>>>>>>> verwende
>>>>>>>>>>>>> ich ein 64-Bit Suse 11 Linux.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Was kann ich tun, um das Problem zu beheben?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sorry, dass ich Sie direkt anschreibe, habe auf der Homepage
>>>>>>>>>>>>> nach
>>>>>>>>>>>>> einem
>>>>>>>>>>>>> Link für eine Mailingliste gesucht, aber hab ihn leider nicht
>>>>>>>>>>>>> gefunden...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Wäre prima, wenn Sie mir irgendwie weiterhelfen könnten .
>>>>>>>>>>>>>
>>>>>>>>>>>>> == 09:42:36 =[1]=> Building archiver/tar [1.22 8.0-trunk].
>>>>>>>>>>>>> -> Parallel build using 2 jobs enabled.
>>>>>>>>>>>>> -> Reading package config: package/archiver/tar/tar.conf
>>>>>>>>>>>>> -> Preparing build in
>>>>>>>>>>>>> src.tar.default.20090318.094235.8777.nexoc
>>>>>>>>>>>>> -> Building. Writing output to $root/var/adm/logs/1-tar.out
>>>>>>>>>>>>> !> checking whether program_invocation_name is declared... yes
>>>>>>>>>>>>> !> checking whether program_invocation_short_name is
>>>>>>>>>>>>> declared... yes
>>>>>>>>>>>>> !> checking whether program_invocation_name is defined... yes
>>>>>>>>>>>>> !> checking whether program_invocation_short_name is
>>>>>>>>>>>>> defined...
>>>>>>>>>>>>> yes
>>>>>>>>>>>>> !> checking whether btowc(EOF) is correct... configure: error:
>>>>>>>>>>>>> cannot
>>>>>>>>>>>>> run test program while cross compiling
>>>>>>>>>>>>> !> See `config.log' for more details.
>>>>>>>>>>>>> !> Due to previous errors, no 1-tar.log file!
>>>>>>>>>>>>> !> (Try enabling xtrace in the config to track an error
>>>>>>>>>>>>> inside the
>>>>>>>>>>>>> build
>>>>>>>>>>>>> system.)
>>>>>>>>>>>>> -> $root/var/adm/logs/1-tar.out -> 1-tar.err
>>>>>>>>>>>>> == 03/18/09 09:43:27 =[1]=> Aborted building package tar.
>>>>>>>>>>>>> -> Unmounting loop mounts ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Vielen Dank im voraus und viele Grüsse
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ingmar Schraub
>>>>>>>>>>>>>                         

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to