|
Problem building C++ program
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Problem building C++ program
by Marian Aldenhövel-2
::
Rate this Message:
Hi,
I am having problems building a custom application written in C++ for my T2 target. While this is not strictly a T2-problem maybe someone here can still give me a push in the right direction. The host is an Ubuntu 8.x system using GCC 4.2.3. The application has been developed on that host and builds fine. When doing the build in T2 I receive the attached ERROR-LOG. It says ::malloc is not defined, which feels pretty basic to me. I also noted the output from configure saying: > checking for GNU libc compatible malloc... no It says "yes" on the host. But then my T2-target is uclibc-based for size. Any ideas on what I might have broken here? Ciao, MM Command Wrapper Debug: running 'i486-t2-linux-uclibc-gcc --version' .. i486-t2-linux-uclibc-gcc is /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/wrapper/i486-t2-linux-uclibc-gcc Old Command: i486-t2-linux-uclibc-gcc --version ENVPREFIX = 'CMD' OTHERS = '' INSERT = '--help?:-pipe -Os -march=i486' REMOVE = '-O -O[0-9s] -mtune* -march* -mcpu* -g*' APPEND = '-s' FILTER = 'sed -e 's,^\(-[LI]\)*\(/\|/usr/\|/usr/[^/]*/\|/opt/[^/]*/\)\(include\|lib\),\1/home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross\2\3,'' conditonal arg: --help?:-pipe. conditonal: --help, lhs: , rhs: -pipe. Insert: -pipe Insert: -Os Insert: -march=i486 Copy: --version Append: -s Run Filter: sed -e 's,^\(-[LI]\)*\(/\|/usr/\|/usr/[^/]*/\|/opt/[^/]*/\)\(include\|lib\),\1/home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross\2\3,' Old PATH: /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/wrapper:/home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/bin:/home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/crosscc:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games New PATH: /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/bin:/home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/crosscc:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games New Command: i486-t2-linux-uclibc-gcc -pipe -Os -march=i486 --version -s i486-t2-linux-uclibc-gcc (GCC) 4.3.4 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [ writing debug log to /home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/cmd_wrapper.log ] `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/archdir/kbox3-HEAD.bz2' -> `/home/kbox/t2/download/mirror/k/kbox3-HEAD.bz2' Running main build function 'build_this_package' ... Extracting kbox3-HEAD.bz2 (--use-compress-program=bzip2 -xf) ... Fixing ownership and permissions ... Removing CVS, .svn, {arch} and .arch-ids directories ... Changeing into /home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3 ... Bootstrapping the GNU autotools... Apply patch /home/kbox/t2/package/contrib/kbox3/configure.patch ... patching file configure Hunk #1 succeeded at 2151 (offset 8 lines). Creating /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/<..> if required ... Autodetection for option impossible: --disable-debug passed thru. Autodetection for option impossible: --disable-nls passed thru. Autodetection for option impossible: --without-libpam passed thru. Autodetection for option impossible: --without-pam passed thru. Autodetection for option impossible: --disable-libpam passed thru. Autodetection for option impossible: --disable-pam passed thru. Autodetection for option impossible: --enable-efence=no passed thru. Running ./configure --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libdir=/usr/lib --datadir=/usr/share --includedir=/usr/include --infodir=/usr/info --mandir=/usr/man --sysconfdir=/etc --localstatedir=/var --disable-debug --disable-nls --without-libpam --without-pam --disable-libpam --disable-pam --enable-efence=no --with-sqlite3=yes --bindir=\${root}/mnt/kbox --build=i686-nocross-linux-gnu --host=i486-t2-linux-uclibc --cache-file=./config.cache configure: WARNING: unrecognized options: --disable-debug, --disable-nls, --without-libpam, --without-pam, --disable-libpam, --disable-pam, --enable-efence configure: loading cache ./config.cache checking build system type... i686-nocross-linux-gnu checking host system type... i486-t2-linux-uclibc checking target system type... i486-t2-linux-uclibc checking whether #! works in shell scripts... yes checking for gawk... gawk serial ports... unix checking for i486-t2-linux-uclibc-gcc... i486-t2-linux-uclibc-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i486-t2-linux-uclibc-gcc accepts -g... yes checking for i486-t2-linux-uclibc-gcc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether i486-t2-linux-uclibc-g++ accepts -g... yes checking how to run the C preprocessor... i486-t2-linux-uclibc-cpp checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... (cached) yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking sched.h usability... yes checking sched.h presence... yes checking for sched.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking for unistd.h... (cached) yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for error_at_line... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... no checking for strftime... yes checking for gettimeofday... yes checking for memmove... yes checking for memset... yes checking for strerror... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking if pthread_yield is available... no checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for SQLite3 library >= 3.6.0... yes checking for gawk... (cached) gawk checking for curl-config... /usr/local/bin/curl-config checking for the version of libcurl... 7.19.2 checking for libcurl >= version 7.18.0... yes checking whether libcurl is usable... yes checking for curl_free... yes checking for libssl... found headers in /usr/include/openssl checking for log4cxx... found headers in /usr/local/include/log4cxx checking for uuid_generate in -luuid... yes checking for curlpp-config... /usr/local/bin/curlpp-config checking for libcurlpp... using /usr/local/bin/curlpp-config checking for a BSD-compatible install... /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/TOOLCHAIN/tools.cross/wrapper/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for i486-t2-linux-uclibc-strip... i486-t2-linux-uclibc-strip checking dependency style of i486-t2-linux-uclibc-gcc... gcc3 checking dependency style of i486-t2-linux-uclibc-g++... gcc3 configure: updating cache ./config.cache configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-debug, --disable-nls, --without-libpam, --without-pam, --disable-libpam, --disable-pam, --enable-efence Running make -j2 CC=i486-t2-linux-uclibc-gcc CPP=i486-t2-linux-uclibc-cpp CXX=i486-t2-linux-uclibc-g++ prefix=/usr CC_FOR_BUILD=cc BUILDCC=cc BUILD_CC=cc HOSTCC=cc HOST_CC=cc STRIP=i486-t2-linux-uclibc-strip AR=i486-t2-linux-uclibc-ar LD=i486-t2-linux-uclibc-ld RANLIB=i486-t2-linux-uclibc-ranlib NM=i486-t2-linux-uclibc-nm make all-recursive make[1]: Entering directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3' Making all in . make[2]: Entering directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3' Making all in src make[2]: Entering directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3/src' i486-t2-linux-uclibc-g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -pthread -I/usr/local/include -I/usr/local/include -I/usr/include/openssl -DHAVE_SSL -I/usr/local/include/log4cxx -DHAVE_LOG4CXX -I/usr/local/include -Wall -Wextra -MT kbox3Main.o -MD -MP -MF .deps/kbox3Main.Tpo -c -o kbox3Main.o kbox3Main.cpp i486-t2-linux-uclibc-g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -pthread -I/usr/local/include -I/usr/local/include -I/usr/include/openssl -DHAVE_SSL -I/usr/local/include/log4cxx -DHAVE_LOG4CXX -I/usr/local/include -Wall -Wextra -MT Thread.o -MD -MP -MF .deps/Thread.Tpo -c -o Thread.o Thread.cpp In file included from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/bits/stl_algo.h:65, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/algorithm:67, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/helpers/tchar.h:25, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/spi/appenderattachable.h:20, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/helpers/appenderattachableimpl.h:20, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/logger.h:22, from Log.h:13, from Exception.h:12, from Thread.cpp:5: /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/cstdlib:124: error: '::malloc' has not been declared In file included from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/bits/stl_algo.h:65, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/algorithm:67, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/helpers/tchar.h:25, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/spi/appenderattachable.h:20, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/helpers/appenderattachableimpl.h:20, from /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/log4cxx/logger.h:22, from Log.h:13, from APServerConnection.h:22, from kbox3Main.cpp:12: /home/kbox/t2/build/kbox-8.0-trunk-kbox-x86-i486-cross/usr/include/c++/4.3.4/cstdlib:124: error: '::malloc' has not been declared make[2]: *** [Thread.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** [kbox3Main.o] Error 1 make[2]: Leaving directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/kbox/t2/src.kbox3.kbox.20091022.112940.18451.kboxdev/kbox3' make: *** [all] Error 2 Due to previous errors, no 1-kbox3.log file! (Try enabling xtrace in the config to track an error inside the build system.) --- BUILD ERROR --- Creating file list and doing final adaptions ... Searching for orphaned files ... Found 6 files for this package. Found 1 orphaned files for this package. Clear (old) md5sums ... Creating md5sum files ... done. Creating package description ... Making post-install adaptions. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Build-Pkg mine is OK, but fails under Build-Target
by Bob Gustafson
::
Rate this Message:
Reading some of the handbook, it seems that Build-Pkg does not check dependencies, but that Build-Target does (??) Perhaps this is the problem. mine fails looking for dialog.h There are lots of dialog.h files sprinkled around in the t2-trunk directory, and there is a [DEP] dialog in the mine.cache file. ./scripts/Build-Pkg mine works fine: == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. -> Reading package config: package/archiver/mine/mine.conf -> Preparing build in src.mine.default.20091022.132759.329.susie -> Building. Writing output to $root/var/adm/logs/9-mine.out -> $root/var/adm/logs/9-mine.out -> 9-mine.log == 10/22/09 13:30:02 =[9]=> Finished building package mine. root@susie:/usr/local/src/t2-trunk# The local var/adm/logs directory shows an err file which happened about ten minutes ago during the Build-Target run and a much older 0-mine.log file Note that the 9-mine.log file from the above Build-Pkg run appears in the system root directory /var/adm/logs These things are a puzzle to me. Why are these files scattered around and more importantly, why is mine failing to build under Build-Target? =========== The /var/adm/log root@susie:/usr/local/src/t2-trunk/build/default-8.0-trunk-generic-x86-i486-linux/var/adm/logs# ls -l | grep mine -rw-r--r-- 1 root root 20409 Oct 19 14:31 0-mine.log -rw-r--r-- 1 root root 24579 Oct 22 13:11 1-mine.err root@susie:/usr/local/src/t2-trunk/build/default-8.0-trunk-generic-x86-i486-linux/var/adm/logs# ls -l /var/adm/logs | grep mine -rw-r--r-- 1 root root 19427 Oct 22 13:30 9-mine.log ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target
by René Rebe
::
Rate this Message:
Hi,
On 22.10.2009, at 20:41, Bob Gustafson wrote:
Neither does. Emerge-Pkg does, but it is only meant for in-system package installation and updates.
Build-Pkg without any other option installs into your running system (like Emerge-Pkg).
That's the default of Build-Pkg. You would need to specify some more options like -chroot and -root etc to exactly mimic what happens during the target build.
Because then it builds in the cross compile / sandbox, most probably some dependency or so is missing. I also recently changed mine to cross compile with the gasgui fronted, because I needed that. Maybe a typo slipped in. What kind of target and configuration do you build? -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target
by Bob Gustafson
::
Rate this Message:
I am just following the Documentation and am trying to build the T2 system itself. My build system was a small old laptop which seemed to trundle on ok, except when the Build-Target couldn't find dialog.h I now have a new system which has the Intel virtual bit and lots of horsepower. Just brought it up a couple of hours ago running Fedora-12-Beta. F12 seems to install and run pretty well, even with hardware RAID, which was a problem with Fedora-11 My intention is to bring up T2 as a virtual client with Fedora-12 as the base. Lots of moving parts at the moment though. I would appreciate if you would take a look at the Build-Target of the current t2-trunk as it is in svn. My build broke in mine where it could not find the dialog package. I sent several emails to the list detailing my progress and problem. Thanks for your clues. I will take them into account when I get my virtual T2 client installed. Bob G On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: > Hi, > > On 22.10.2009, at 20:41, Bob Gustafson wrote: > > > Reading some of the handbook, it seems that Build-Pkg does not check > > dependencies, but that Build-Target does (??) Perhaps this is the > > problem. > > > > > Neither does. Emerge-Pkg does, but it is only meant for in-system > package installation and updates. > > > mine fails looking for dialog.h > > > > There are lots of dialog.h files sprinkled around in the t2-trunk > > directory, and there is a [DEP] dialog in the mine.cache file. > > > > ./scripts/Build-Pkg mine works fine: > > > > == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. > > -> Reading package config: package/archiver/mine/mine.conf > > -> Preparing build in src.mine.default.20091022.132759.329.susie > > -> Building. Writing output to $root/var/adm/logs/9-mine.out > > -> $root/var/adm/logs/9-mine.out -> 9-mine.log > > == 10/22/09 13:30:02 =[9]=> Finished building package mine > > > > > Build-Pkg without any other option installs into your running system > (like Emerge-Pkg). > > > The local var/adm/logs directory shows an err file which happened > > about > > ten minutes ago during the Build-Target run and a much older > > 0-mine.log file > > > > Note that the 9-mine.log file from the above Build-Pkg run appears > > in > > the system root directory /var/adm/logs > > > > > That's the default of Build-Pkg. You would need to specify some more > options like -chroot and -root etc to exactly mimic what happens > during the target build. > > > These things are a puzzle to me. Why are these files scattered > > around > > and more importantly, why is mine failing to build under > > Build-Target? > > > > > Because then it builds in the cross compile / sandbox, most probably > some dependency or so is missing. I also recently changed mine to > cross compile with the gasgui fronted, because I needed that. Maybe a > typo slipped in. > > > What kind of target and configuration do you build? > > -- > René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin > http://exactcode.com | http://t2-project.org | http://rene.rebe.name > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target
by Mika Pesu
::
Rate this Message:
Hi,
I noticed this my self too, the key is to include dialog package as well and modify it's build stages and priority. Dont remember offhand but i think dialog package was missing stage 1 build and it's build priority was after mine package. I think this was the cause of mine build fail, that it is, if you get the same error on stage 1 mine build. I can't commit the changes my self to svn at the moment, but if someone with svn write access could do it and verify dialog build options that those are right. -Mika Bob Gustafson kirjoitti: > I am just following the Documentation and am trying to build the T2 > system itself. My build system was a small old laptop which seemed to > trundle on ok, except when the Build-Target couldn't find dialog.h > > I now have a new system which has the Intel virtual bit and lots of > horsepower. Just brought it up a couple of hours ago running > Fedora-12-Beta. F12 seems to install and run pretty well, even with > hardware RAID, which was a problem with Fedora-11 > > My intention is to bring up T2 as a virtual client with Fedora-12 as the > base. Lots of moving parts at the moment though. > > I would appreciate if you would take a look at the Build-Target of the > current t2-trunk as it is in svn. My build broke in mine where it could > not find the dialog package. I sent several emails to the list detailing > my progress and problem. > > Thanks for your clues. I will take them into account when I get my > virtual T2 client installed. > > Bob G > > > On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: > >> Hi, >> >> On 22.10.2009, at 20:41, Bob Gustafson wrote: >> >> >>> Reading some of the handbook, it seems that Build-Pkg does not check >>> dependencies, but that Build-Target does (??) Perhaps this is the >>> problem. >>> >>> >> Neither does. Emerge-Pkg does, but it is only meant for in-system >> package installation and updates. >> >> >>> mine fails looking for dialog.h >>> >>> There are lots of dialog.h files sprinkled around in the t2-trunk >>> directory, and there is a [DEP] dialog in the mine.cache file. >>> >>> ./scripts/Build-Pkg mine works fine: >>> >>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. >>> -> Reading package config: package/archiver/mine/mine.conf >>> -> Preparing build in src.mine.default.20091022.132759.329.susie >>> -> Building. Writing output to $root/var/adm/logs/9-mine.out >>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log >>> == 10/22/09 13:30:02 =[9]=> Finished building package mine >>> >>> >> Build-Pkg without any other option installs into your running system >> (like Emerge-Pkg). >> >> >>> The local var/adm/logs directory shows an err file which happened >>> about >>> ten minutes ago during the Build-Target run and a much older >>> 0-mine.log file >>> >>> Note that the 9-mine.log file from the above Build-Pkg run appears >>> in >>> the system root directory /var/adm/logs >>> >>> >> That's the default of Build-Pkg. You would need to specify some more >> options like -chroot and -root etc to exactly mimic what happens >> during the target build. >> >> >>> These things are a puzzle to me. Why are these files scattered >>> around >>> and more importantly, why is mine failing to build under >>> Build-Target? >>> >>> >> Because then it builds in the cross compile / sandbox, most probably >> some dependency or so is missing. I also recently changed mine to >> cross compile with the gasgui fronted, because I needed that. Maybe a >> typo slipped in. >> >> >> What kind of target and configuration do you build? >> >> -- >> René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin >> http://exactcode.com | http://t2-project.org | http://rene.rebe.name >> >> >> > > > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > lists@... with a subject of: unsubscribe t2 > > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target
by Bob Gustafson
::
Rate this Message:
Hi Mika If you can just post your changes to the list, I'm sure that they will find their way into the t2-trunk. The dialog package is listed as a dependency to mine, but it isn't being built. Your comments seem right on. Bob G On Mon, 2009-10-26 at 19:45 +0200, Mika Pesu wrote: > Hi, > > I noticed this my self too, the key is to include dialog package as well > and modify it's build stages and priority. Dont remember offhand but i > think dialog package was missing stage 1 build and it's build priority > was after mine package. I think this was the cause of mine build fail, > that it is, if you get the same error on stage 1 mine build. > > I can't commit the changes my self to svn at the moment, but if someone > with svn write access could do it and verify dialog build options that > those are right. > > -Mika > > > Bob Gustafson kirjoitti: > > I am just following the Documentation and am trying to build the T2 > > system itself. My build system was a small old laptop which seemed to > > trundle on ok, except when the Build-Target couldn't find dialog.h > > > > I now have a new system which has the Intel virtual bit and lots of > > horsepower. Just brought it up a couple of hours ago running > > Fedora-12-Beta. F12 seems to install and run pretty well, even with > > hardware RAID, which was a problem with Fedora-11 > > > > My intention is to bring up T2 as a virtual client with Fedora-12 as the > > base. Lots of moving parts at the moment though. > > > > I would appreciate if you would take a look at the Build-Target of the > > current t2-trunk as it is in svn. My build broke in mine where it could > > not find the dialog package. I sent several emails to the list detailing > > my progress and problem. > > > > Thanks for your clues. I will take them into account when I get my > > virtual T2 client installed. > > > > Bob G > > > > > > On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: > > > >> Hi, > >> > >> On 22.10.2009, at 20:41, Bob Gustafson wrote: > >> > >> > >>> Reading some of the handbook, it seems that Build-Pkg does not check > >>> dependencies, but that Build-Target does (??) Perhaps this is the > >>> problem. > >>> > >>> > >> Neither does. Emerge-Pkg does, but it is only meant for in-system > >> package installation and updates. > >> > >> > >>> mine fails looking for dialog.h > >>> > >>> There are lots of dialog.h files sprinkled around in the t2-trunk > >>> directory, and there is a [DEP] dialog in the mine.cache file. > >>> > >>> ./scripts/Build-Pkg mine works fine: > >>> > >>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. > >>> -> Reading package config: package/archiver/mine/mine.conf > >>> -> Preparing build in src.mine.default.20091022.132759.329.susie > >>> -> Building. Writing output to $root/var/adm/logs/9-mine.out > >>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log > >>> == 10/22/09 13:30:02 =[9]=> Finished building package mine > >>> > >>> > >> Build-Pkg without any other option installs into your running system > >> (like Emerge-Pkg). > >> > >> > >>> The local var/adm/logs directory shows an err file which happened > >>> about > >>> ten minutes ago during the Build-Target run and a much older > >>> 0-mine.log file > >>> > >>> Note that the 9-mine.log file from the above Build-Pkg run appears > >>> in > >>> the system root directory /var/adm/logs > >>> > >>> > >> That's the default of Build-Pkg. You would need to specify some more > >> options like -chroot and -root etc to exactly mimic what happens > >> during the target build. > >> > >> > >>> These things are a puzzle to me. Why are these files scattered > >>> around > >>> and more importantly, why is mine failing to build under > >>> Build-Target? > >>> > >>> > >> Because then it builds in the cross compile / sandbox, most probably > >> some dependency or so is missing. I also recently changed mine to > >> cross compile with the gasgui fronted, because I needed that. Maybe a > >> typo slipped in. > >> > >> > >> What kind of target and configuration do you build? > >> > >> -- > >> René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin > >> http://exactcode.com | http://t2-project.org | http://rene.rebe.name > >> > >> > >> > > > > > > > > ----------------------------------------------------------- > > If you wish to unsubscribe from this mailing, send mail to > > lists@... with a subject of: unsubscribe t2 > > > > > > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target]
by Mika Pesu
::
Rate this Message:
Hi
I attached util-linux and dialog patches. Dont really remember why i have also changed util-linux build priority, but the attached dialog patch priority should fix the mine package build. -Mika Bob Gustafson kirjoitti: > Hi Mika > > If you can just post your changes to the list, I'm sure that they will > find their way into the t2-trunk. > > The dialog package is listed as a dependency to mine, but it isn't being > built. Your comments seem right on. > > Bob G > > On Mon, 2009-10-26 at 19:45 +0200, Mika Pesu wrote: > >> Hi, >> >> I noticed this my self too, the key is to include dialog package as well >> and modify it's build stages and priority. Dont remember offhand but i >> think dialog package was missing stage 1 build and it's build priority >> was after mine package. I think this was the cause of mine build fail, >> that it is, if you get the same error on stage 1 mine build. >> >> I can't commit the changes my self to svn at the moment, but if someone >> with svn write access could do it and verify dialog build options that >> those are right. >> >> -Mika >> >> >> Bob Gustafson kirjoitti: >> >>> I am just following the Documentation and am trying to build the T2 >>> system itself. My build system was a small old laptop which seemed to >>> trundle on ok, except when the Build-Target couldn't find dialog.h >>> >>> I now have a new system which has the Intel virtual bit and lots of >>> horsepower. Just brought it up a couple of hours ago running >>> Fedora-12-Beta. F12 seems to install and run pretty well, even with >>> hardware RAID, which was a problem with Fedora-11 >>> >>> My intention is to bring up T2 as a virtual client with Fedora-12 as the >>> base. Lots of moving parts at the moment though. >>> >>> I would appreciate if you would take a look at the Build-Target of the >>> current t2-trunk as it is in svn. My build broke in mine where it could >>> not find the dialog package. I sent several emails to the list detailing >>> my progress and problem. >>> >>> Thanks for your clues. I will take them into account when I get my >>> virtual T2 client installed. >>> >>> Bob G >>> >>> >>> On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: >>> >>> >>>> Hi, >>>> >>>> On 22.10.2009, at 20:41, Bob Gustafson wrote: >>>> >>>> >>>> >>>>> Reading some of the handbook, it seems that Build-Pkg does not check >>>>> dependencies, but that Build-Target does (??) Perhaps this is the >>>>> problem. >>>>> >>>>> >>>>> >>>> Neither does. Emerge-Pkg does, but it is only meant for in-system >>>> package installation and updates. >>>> >>>> >>>> >>>>> mine fails looking for dialog.h >>>>> >>>>> There are lots of dialog.h files sprinkled around in the t2-trunk >>>>> directory, and there is a [DEP] dialog in the mine.cache file. >>>>> >>>>> ./scripts/Build-Pkg mine works fine: >>>>> >>>>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. >>>>> -> Reading package config: package/archiver/mine/mine.conf >>>>> -> Preparing build in src.mine.default.20091022.132759.329.susie >>>>> -> Building. Writing output to $root/var/adm/logs/9-mine.out >>>>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log >>>>> == 10/22/09 13:30:02 =[9]=> Finished building package mine >>>>> >>>>> >>>>> >>>> Build-Pkg without any other option installs into your running system >>>> (like Emerge-Pkg). >>>> >>>> >>>> >>>>> The local var/adm/logs directory shows an err file which happened >>>>> about >>>>> ten minutes ago during the Build-Target run and a much older >>>>> 0-mine.log file >>>>> >>>>> Note that the 9-mine.log file from the above Build-Pkg run appears >>>>> in >>>>> the system root directory /var/adm/logs >>>>> >>>>> >>>>> >>>> That's the default of Build-Pkg. You would need to specify some more >>>> options like -chroot and -root etc to exactly mimic what happens >>>> during the target build. >>>> >>>> >>>> >>>>> These things are a puzzle to me. Why are these files scattered >>>>> around >>>>> and more importantly, why is mine failing to build under >>>>> Build-Target? >>>>> >>>>> >>>>> >>>> Because then it builds in the cross compile / sandbox, most probably >>>> some dependency or so is missing. I also recently changed mine to >>>> cross compile with the gasgui fronted, because I needed that. Maybe a >>>> typo slipped in. >>>> >>>> >>>> What kind of target and configuration do you build? >>>> >>>> -- >>>> René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin >>>> http://exactcode.com | http://t2-project.org | http://rene.rebe.name >>>> >>>> >>>> >>>> >>> >>> ----------------------------------------------------------- >>> If you wish to unsubscribe from this mailing, send mail to >>> lists@... with a subject of: unsubscribe t2 >>> >>> >>> >>> > > > Index: package/base/dialog/dialog.desc =================================================================== --- package/base/dialog/dialog.desc (revision 34726) +++ package/base/dialog/dialog.desc (working copy) @@ -36,6 +36,6 @@ [L] GPL [S] Stable [V] 1.0-20050911 -[P] X -----5---9 113.900 +[P] X -1---5---9 113.900 [D] 1535550711 dialog-1.0-20050911.tgz ftp://invisible-island.net/dialog/ Index: package/base/util-linux/util-linux.desc =================================================================== --- package/base/util-linux/util-linux.desc (revision 34726) +++ package/base/util-linux/util-linux.desc (working copy) @@ -29,6 +29,6 @@ [L] GPL [S] Stable [V] 2.16.1 -[P] X -1-3-----9 115.000 +[P] X -1-3-----9 112.000 [D] 1920311447 util-linux-ng-2.16.1.tar.bz2 ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.16/ ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target]
by Bob Gustafson
::
Rate this Message:
Super. Your one character changes to each of two files did the trick. It is now compiling Build-Target and is well past the mine (field) after recompiling base/util-linux and /base/dialog Still building on the old laptop so it will be awhile before I know if it goes to the end. I am working with svn update of t2-trunk as of a few minutes ago. Thanks again for your patch. Bob G On Tue, 2009-10-27 at 16:04 +0200, Mika Pesu wrote: > Hi > > I attached util-linux and dialog patches. Dont really remember why i > have also changed util-linux build priority, but the attached dialog > patch priority should fix the mine package build. > > -Mika > > > Bob Gustafson kirjoitti: > > Hi Mika > > > > If you can just post your changes to the list, I'm sure that they will > > find their way into the t2-trunk. > > > > The dialog package is listed as a dependency to mine, but it isn't being > > built. Your comments seem right on. > > > > Bob G > > > > On Mon, 2009-10-26 at 19:45 +0200, Mika Pesu wrote: > > > >> Hi, > >> > >> I noticed this my self too, the key is to include dialog package as well > >> and modify it's build stages and priority. Dont remember offhand but i > >> think dialog package was missing stage 1 build and it's build priority > >> was after mine package. I think this was the cause of mine build fail, > >> that it is, if you get the same error on stage 1 mine build. > >> > >> I can't commit the changes my self to svn at the moment, but if someone > >> with svn write access could do it and verify dialog build options that > >> those are right. > >> > >> -Mika > >> > >> > >> Bob Gustafson kirjoitti: > >> > >>> I am just following the Documentation and am trying to build the T2 > >>> system itself. My build system was a small old laptop which seemed to > >>> trundle on ok, except when the Build-Target couldn't find dialog.h > >>> > >>> I now have a new system which has the Intel virtual bit and lots of > >>> horsepower. Just brought it up a couple of hours ago running > >>> Fedora-12-Beta. F12 seems to install and run pretty well, even with > >>> hardware RAID, which was a problem with Fedora-11 > >>> > >>> My intention is to bring up T2 as a virtual client with Fedora-12 as the > >>> base. Lots of moving parts at the moment though. > >>> > >>> I would appreciate if you would take a look at the Build-Target of the > >>> current t2-trunk as it is in svn. My build broke in mine where it could > >>> not find the dialog package. I sent several emails to the list detailing > >>> my progress and problem. > >>> > >>> Thanks for your clues. I will take them into account when I get my > >>> virtual T2 client installed. > >>> > >>> Bob G > >>> > >>> > >>> On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: > >>> > >>> > >>>> Hi, > >>>> > >>>> On 22.10.2009, at 20:41, Bob Gustafson wrote: > >>>> > >>>> > >>>> > >>>>> Reading some of the handbook, it seems that Build-Pkg does not check > >>>>> dependencies, but that Build-Target does (??) Perhaps this is the > >>>>> problem. > >>>>> > >>>>> > >>>>> > >>>> Neither does. Emerge-Pkg does, but it is only meant for in-system > >>>> package installation and updates. > >>>> > >>>> > >>>> > >>>>> mine fails looking for dialog.h > >>>>> > >>>>> There are lots of dialog.h files sprinkled around in the t2-trunk > >>>>> directory, and there is a [DEP] dialog in the mine.cache file. > >>>>> > >>>>> ./scripts/Build-Pkg mine works fine: > >>>>> > >>>>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. > >>>>> -> Reading package config: package/archiver/mine/mine.conf > >>>>> -> Preparing build in src.mine.default.20091022.132759.329.susie > >>>>> -> Building. Writing output to $root/var/adm/logs/9-mine.out > >>>>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log > >>>>> == 10/22/09 13:30:02 =[9]=> Finished building package mine > >>>>> > >>>>> > >>>>> > >>>> Build-Pkg without any other option installs into your running system > >>>> (like Emerge-Pkg). > >>>> > >>>> > >>>> > >>>>> The local var/adm/logs directory shows an err file which happened > >>>>> about > >>>>> ten minutes ago during the Build-Target run and a much older > >>>>> 0-mine.log file > >>>>> > >>>>> Note that the 9-mine.log file from the above Build-Pkg run appears > >>>>> in > >>>>> the system root directory /var/adm/logs > >>>>> > >>>>> > >>>>> > >>>> That's the default of Build-Pkg. You would need to specify some more > >>>> options like -chroot and -root etc to exactly mimic what happens > >>>> during the target build. > >>>> > >>>> > >>>> > >>>>> These things are a puzzle to me. Why are these files scattered > >>>>> around > >>>>> and more importantly, why is mine failing to build under > >>>>> Build-Target? > >>>>> > >>>>> > >>>>> > >>>> Because then it builds in the cross compile / sandbox, most probably > >>>> some dependency or so is missing. I also recently changed mine to > >>>> cross compile with the gasgui fronted, because I needed that. Maybe a > >>>> typo slipped in. > >>>> > >>>> > >>>> What kind of target and configuration do you build? > >>>> > >>>> -- > >>>> René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin > >>>> http://exactcode.com | http://t2-project.org | http://rene.rebe.name > >>>> > >>>> > >>>> > >>>> > >>> > >>> ----------------------------------------------------------- > >>> If you wish to unsubscribe from this mailing, send mail to > >>> lists@... with a subject of: unsubscribe t2 > >>> > >>> > >>> > >>> > > > > > > > > plain text document attachment (dialog.patch) > Index: package/base/dialog/dialog.desc > =================================================================== > --- package/base/dialog/dialog.desc (revision 34726) > +++ package/base/dialog/dialog.desc (working copy) > @@ -36,6 +36,6 @@ > [L] GPL > [S] Stable > [V] 1.0-20050911 > -[P] X -----5---9 113.900 > +[P] X -1---5---9 113.900 > > [D] 1535550711 dialog-1.0-20050911.tgz ftp://invisible-island.net/dialog/ > plain text document attachment (util-linux.patch) > Index: package/base/util-linux/util-linux.desc > =================================================================== > --- package/base/util-linux/util-linux.desc (revision 34726) > +++ package/base/util-linux/util-linux.desc (working copy) > @@ -29,6 +29,6 @@ > [L] GPL > [S] Stable > [V] 2.16.1 > -[P] X -1-3-----9 115.000 > +[P] X -1-3-----9 112.000 > > [D] 1920311447 util-linux-ng-2.16.1.tar.bz2 ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.16/ ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
|
|
Re: Build-Pkg mine is OK, but fails under Build-Target]
by René Rebe
::
Rate this Message:
Hi all, dialog part committed: Committed revision 34772. Have fun, Mika Pesu wrote: > Hi > > I attached util-linux and dialog patches. Dont really remember why i > have also changed util-linux build priority, but the attached dialog > patch priority should fix the mine package build. > > -Mika > > > Bob Gustafson kirjoitti: >> Hi Mika >> >> If you can just post your changes to the list, I'm sure that they will >> find their way into the t2-trunk. >> >> The dialog package is listed as a dependency to mine, but it isn't being >> built. Your comments seem right on. >> >> Bob G >> >> On Mon, 2009-10-26 at 19:45 +0200, Mika Pesu wrote: >> >>> Hi, >>> >>> I noticed this my self too, the key is to include dialog package as >>> well and modify it's build stages and priority. Dont remember >>> offhand but i think dialog package was missing stage 1 build and >>> it's build priority was after mine package. I think this was the >>> cause of mine build fail, that it is, if you get the same error on >>> stage 1 mine build. >>> >>> I can't commit the changes my self to svn at the moment, but if >>> someone with svn write access could do it and verify dialog build >>> options that those are right. >>> >>> -Mika >>> >>> >>> Bob Gustafson kirjoitti: >>> >>>> I am just following the Documentation and am trying to build the T2 >>>> system itself. My build system was a small old laptop which seemed to >>>> trundle on ok, except when the Build-Target couldn't find dialog.h >>>> >>>> I now have a new system which has the Intel virtual bit and lots of >>>> horsepower. Just brought it up a couple of hours ago running >>>> Fedora-12-Beta. F12 seems to install and run pretty well, even with >>>> hardware RAID, which was a problem with Fedora-11 >>>> >>>> My intention is to bring up T2 as a virtual client with Fedora-12 >>>> as the >>>> base. Lots of moving parts at the moment though. >>>> >>>> I would appreciate if you would take a look at the Build-Target of the >>>> current t2-trunk as it is in svn. My build broke in mine where it >>>> could >>>> not find the dialog package. I sent several emails to the list >>>> detailing >>>> my progress and problem. >>>> >>>> Thanks for your clues. I will take them into account when I get my >>>> virtual T2 client installed. >>>> >>>> Bob G >>>> >>>> >>>> On Sun, 2009-10-25 at 10:22 +0100, Rene Rebe wrote: >>>> >>>>> Hi, >>>>> >>>>> On 22.10.2009, at 20:41, Bob Gustafson wrote: >>>>> >>>>> >>>>>> Reading some of the handbook, it seems that Build-Pkg does not check >>>>>> dependencies, but that Build-Target does (??) Perhaps this is the >>>>>> problem. >>>>>> >>>>>> >>>>> Neither does. Emerge-Pkg does, but it is only meant for in-system >>>>> package installation and updates. >>>>> >>>>> >>>>>> mine fails looking for dialog.h >>>>>> >>>>>> There are lots of dialog.h files sprinkled around in the t2-trunk >>>>>> directory, and there is a [DEP] dialog in the mine.cache file. >>>>>> >>>>>> ./scripts/Build-Pkg mine works fine: >>>>>> >>>>>> == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. >>>>>> -> Reading package config: package/archiver/mine/mine.conf >>>>>> -> Preparing build in src.mine.default.20091022.132759.329.susie >>>>>> -> Building. Writing output to $root/var/adm/logs/9-mine.out >>>>>> -> $root/var/adm/logs/9-mine.out -> 9-mine.log >>>>>> == 10/22/09 13:30:02 =[9]=> Finished building package mine >>>>>> >>>>>> >>>>> Build-Pkg without any other option installs into your running system >>>>> (like Emerge-Pkg). >>>>> >>>>> >>>>>> The local var/adm/logs directory shows an err file which happened >>>>>> about >>>>>> ten minutes ago during the Build-Target run and a much older >>>>>> 0-mine.log file >>>>>> >>>>>> Note that the 9-mine.log file from the above Build-Pkg run appears >>>>>> in >>>>>> the system root directory /var/adm/logs >>>>>> >>>>>> >>>>> That's the default of Build-Pkg. You would need to specify some more >>>>> options like -chroot and -root etc to exactly mimic what happens >>>>> during the target build. >>>>> >>>>> >>>>>> These things are a puzzle to me. Why are these files scattered >>>>>> around >>>>>> and more importantly, why is mine failing to build under >>>>>> Build-Target? >>>>>> >>>>>> >>>>> Because then it builds in the cross compile / sandbox, most probably >>>>> some dependency or so is missing. I also recently changed mine to >>>>> cross compile with the gasgui fronted, because I needed that. Maybe a >>>>> typo slipped in. >>>>> >>>>> >>>>> What kind of target and configuration do you build? >>>>> >>>>> -- >>>>> René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin >>>>> http://exactcode.com | http://t2-project.org | >>>>> http://rene.rebe.name >>>>> >>>>> >>>>> >>>> >>>> ----------------------------------------------------------- If you >>>> wish to unsubscribe from this mailing, send mail to >>>> lists@... with a subject of: unsubscribe t2 >>>> >>>> >>>> >> >> >> > -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10785 Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to lists@... with a subject of: unsubscribe t2 |
| Free embeddable forum powered by Nabble | Forum Help |
