OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: BerndS on January 21, 2009, 03:37:24 pm
-
Hi,
which packages do I need to compile Qt3 programs for Angstrom/Opie ? And where can I get them?
(I want to compile portabase for Angstrom with Opie)
regards
Bernd
-
Searching here: http://www.angstrom-distribution.org/repo/ (http://www.angstrom-distribution.org/repo/)
I found that libqpe-dev is probably what you want. I didn't see anything that looked correct for QT stuff. It looked to mostly be for X11. Feel free to search again, though, and I don't know if what I found is what you need or not.
I searched for things like:
qt
qt3
qpe
-
Hi,
which packages do I need to compile Qt3 programs for Angstrom/Opie ? And where can I get them?
(I want to compile portabase for Angstrom with Opie)
Given the fact that opie completely relies on qte 2.3.x you need a very good programmer who ports the missing qt3 functionality to qt2.
Though last time I checked portabase was based on qt2, not qt3.
And if you want to build angstrom packages, why don't you hop over to http://www.openembedded.org (http://www.openembedded.org) and read the "Getting Started" instructions ?
Oliver
-
Hi,
which packages do I need to compile Qt3 programs for Angstrom/Opie ? And where can I get them?
(I want to compile portabase for Angstrom with Opie)
Given the fact that opie completely relies on qte 2.3.x you need a very good programmer who ports the missing qt3 functionality to qt2.
Though last time I checked portabase was based on qt2, not qt3.
ok, then I need packages with the libraries and tools for qt2.
And if you want to build angstrom packages, why don't you hop over to http://www.openembedded.org (http://www.openembedded.org) and read the "Getting Started" instructions ?
Already been there - but I did not find the infos I want. I do not want to write new programs for Opie or create a new image - just compile the existing Portabase for Opie on my Zaurus.
Bernd
-
And if you want to build angstrom packages, why don't you hop over to http://www.openembedded.org (http://www.openembedded.org) and read the "Getting Started" instructions ?
Already been there - but I did not find the infos I want. I do not want to write new programs for Opie or create a new image - just compile the existing Portabase for Opie on my Zaurus.
In that case you missed the point. OE is a complete build system for automatically building the software be it the whole Angstrom distribution or only packages. In any case it fetches the required dependencies and sets up the cross compiling system. If you want to build a package for Angstrom there is no good way around setting up OE.
Oliver
-
In that case you missed the point. OE is a complete build system for automatically building the software be it the whole Angstrom distribution or only packages. In any case it fetches the required dependencies and sets up the cross compiling system. If you want to build a package for Angstrom there is no good way around setting up OE.
ok; but then: How can I build the binaries for an application for OPIE?
From the other messages in this thread I read that Portabase should run under OPIE -- if I only could compile it.
regards
Bernd
-
ok; but then: How can I build the binaries for an application for OPIE?
From the other messages in this thread I read that Portabase should run under OPIE -- if I only could compile it.
Bernd, the build process is completety described in the Angstrom and OE wiki and Getting Started sections.
Once you have set up OE it is as simple as calling "bitbake portabase"
However be aware that nobody has build portabase for a while- as it requires several dependencies they might have broken in the meantime and are then not compatible any more with the current Angstrom version. In that case some hacking is required.
Oliver
-
Oliver,
after rereading the Angstrom and OE wiki I installed bitbake on my Thinkpad running Ubuntu (Hardy Heron). And in principle it works -- after installing and configuring bitbake like described here http://wiki.openembedded.net/index.php/Getting_Started (http://wiki.openembedded.net/index.php/Getting_Started) a "bitbake opie-image" created a new image and "bitbake portabase" created a portabase package file.
Perfect...
Then I created a new directory to create the image for angstrom-2007.1 and a Portabase package for my current Opie environment on the Zaurus like it's described here http://www.angstrom-distribution.org/building-angstrom (http://www.angstrom-distribution.org/building-angstrom).
In this directory bitbake does not work as expected; I always get the error message
[angstrom-2007.1] xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/org.openembedded.stable$ bitbake opie-image
NOTE: Out of date cache found, rebuilding...
NOTE: Handling BitBake files: | (4976/4976) [100 %]
NOTE: Parsing finished. 0 cached, 4751 parsed, 225 skipped, 0 masked.
NOTE: build 200901262327: started
OE Build Configuration:
BB_VERSION = "1.8.12"
OE_REVISION = "<unknown>"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "c7x0"
DISTRO = "angstrom"
DISTRO_VERSION = "2007.12-r19"
TARGET_FPU = "soft"
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-gnueabi-libc-for-gcc)
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/arm-angstrom-linux-gnueabi-gcc-2.95']
(and some other error messages which are follow-up errors I think).
My local.conf file is
DL_DIR = "/data/develop/oe/angstrom-2007.1/sources"
BBFILES = "/data/develop/oe/angstrom-2007.1/org.openembedded.stable/packages/*/*.bb"
BBMASK = ""
CCACHE=""
PREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie"
PREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-intermediate:gcc-cross-intermediate"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross"
TMPDIR = "/data/develop/oe/angstrom-2007.1/oetmp"
MACHINE = "c7x0"
DISTRO = "angstrom-2007.1"
IMAGE_FSTYPES = "jffs2 tar.gz"
BBINCLUDELOGS = "yes"
and BBPATH is
[angstrom-2007.1] xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/org.openembedded.stable$ echo $BBPATH
/data/develop/oe/angstrom-2007.1/build:/data/develop/oe/angstrom-2007.1/org.openembedded.stable
Unfortunately the documentation for bitbake is not that good so I'm lost here .. Any clues?
regards
Bernd
Update:
Just read in a message that this message can be ignored ... therefor I add all messages I get:
[angstrom-2007.1] xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$ bitbake opie-image
NOTE: Handling BitBake files: | (4976/4976) [100 %]
NOTE: Parsing finished. 4750 cached, 1 parsed, 225 skipped, 0 masked.
NOTE: build 200901270958: started
OE Build Configuration:
BB_VERSION = "1.8.12"
OE_REVISION = "<unknown>"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "c7x0"
DISTRO = "angstrom"
DISTRO_VERSION = "2007.12-r19"
TARGET_FPU = "soft"
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-gnueabi-libc-for-gcc)
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'virtual/arm-angstrom-linux-gnueabi-gcc-2.95' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/arm-angstrom-linux-gnueabi-gcc-2.95']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-64-0' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-64-0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-64-0']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-24-8' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-24-8' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-24-8']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-32-0' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-32-0' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-32-0']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-32-32' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-32-32' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-32-32']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-40-24' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-40-24' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-40-24']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-48-16' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-48-16' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-48-16']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'collie-kernel-58-6' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'collie-kernel-58-6' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['collie-kernel-58-6']
ERROR: '[]' RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity 'pango-directfb' but it wasn't found in any PACKAGE or RPROVIDES variables
NOTE: Runtime target 'pango-directfb' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pango-directfb']
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 6 of 2467 (ID: 19, /data/develop/oe/angstrom-2007.1/org.openembedded.stable/packages/shasum/shasum-native.bb, do_compile)
NOTE: package shasum-native-1.0: started
NOTE: package shasum-native-1.0-r1: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows (/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1/temp/log.do_compile.16666)
| collect2: cannot find 'ld'
NOTE: Task failed: /data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1/temp/log.do_compile.16666
NOTE: package shasum-native-1.0-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package shasum-native-1.0: failed
ERROR: Build of /data/develop/oe/angstrom-2007.1/org.openembedded.stable/packages/shasum/shasum-native.bb do_compile failed
ERROR: Task 19 (/data/develop/oe/angstrom-2007.1/org.openembedded.stable/packages/shasum/shasum-native.bb, do_compile) failed
NOTE: Tasks Summary: Attempted 5 tasks of which 5 didn't need to be rerun and 1 failed.
ERROR: '/data/develop/oe/angstrom-2007.1/org.openembedded.stable/packages/shasum/shasum-native.bb' failed
NOTE: build 200901270958: completed
[angstrom-2007.1] xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$
-
The error is here:
ERROR: log data follows (/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1/temp/log.do_compile.16666)
| collect2: cannot find 'ld'
It is looking for the native linker which lets me believe that your native machine does not have a compiler/linker package installed.
Oliver
-
The error is here:
It is looking for the native linker which lets me believe that your native machine does not have a compiler/linker package installed.
The gcc is installed and working (I already compiled angstrom 2008.1 without problems) . The main problem seems to be that gcc when called via bitbake does not find ld. But ld is installed and available via the PATH variable:
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$ which gcc
/usr/bin/gcc
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$ which ld
/usr/bin/ld
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$ ls -lL /usr/bin/gcc /usr/bin/ld
-rwxr-xr-x 1 root root 222688 Oct 11 06:24 /usr/bin/gcc
-rwxr-xr-x 1 root root 457416 Jan 3 2008 /usr/bin/ld
So I don't know why ld is not found.
Doing the compile manually with the commands from the log works also:
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/build$ cd /data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1$ ls
main.c mhash_sha256.h sha256.c temp
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1$ gcc -isystem/data/develop/oe/angstrom-2007.1/oetmp/staging/x86_64-linux/include -Os -isystem/data/develop/oe/angstrom-2007.1/oetmp/staging/x86_64-linux/include -o oe_sha256sum main.c sha256.c
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1$ ls
main.c mhash_sha256.h oe_sha256sum sha256.c temp
xtrnaw7@t61p:/data/develop/oe/angstrom-2007.1/oetmp/work/x86_64-linux/shasum-native-1.0-r1$ ls -l
total 40
-rw-r--r-- 1 xtrnaw7 xtrnaw7 1161 Jan 27 19:23 main.c
-rw-r--r-- 1 xtrnaw7 xtrnaw7 1808 Jan 27 19:23 mhash_sha256.h
-rwxr-xr-x 1 xtrnaw7 xtrnaw7 15236 Jan 27 19:45 oe_sha256sum
-rw-r--r-- 1 xtrnaw7 xtrnaw7 10047 Jan 27 19:23 sha256.c
drwxr-sr-x 2 xtrnaw7 xtrnaw7 4096 Jan 27 19:44 temp
After I wrote my last email I replaced bitbake 1.8.12 with the 1.9 beta and now it seems to work (I will further investigate here to find the real problem)
regards
Bernd
-
Hi
I got it working!
With bitbake version 1.8.10 angstrom-2007.1 compiled without errors! So now I have a self-compiled image and a working portabase for angstrom-2007.1!
I still don't know why bitbake version 1.8.12 does not compile angstrom-2007.1 (bitbake 1.9 beta compiled some parts of angstrom-2007.1 but not all; the error message was the same: ld not found)
Anyway, it works now
regards
Bernd