Hello,
I found similar problems during backporting Qt4 to ptxdist 1.99 series.
I believe the trick is to do a 'make uninstall' for qt. In my case the
'clean' step in rules/qt4.make looks as this:
#
----------------------------------------------------------------------------
# Clean
#
----------------------------------------------------------------------------
qt4_clean:
rm -rf $(STATEDIR)/qt4.*
rm -rf $(PKGDIR)/qt4_*
@cd $(QT4_DIR) && $(QT4_PATH) $(MAKE) uninstall
rm -rf $(QT4_DIR)
If you do a 'ptxdist clean qt4' the sysroot is also cleaned allowing you
to use a proper build.
I also believe that running the 'uninstall' step is a good thing to do
in other packages as well.
Kind regards,
Bart.
On 07/05/2011 09:50 AM, MC Potgieter wrote:
I also had some strange behavior after changing settings for Qt.
I also had to start from scratch to restore order.
Does this mean Arora is now working?
On Tue, Jul 5, 2011 at 9:12 AM, Dave <[email protected]
<mailto:[email protected]>> wrote:
Qt problems on PTXdist 06
After a compilation of my "own" Qt project (/demos/browser), following
instructions posted and adding another mouse driver in Qt things
started
to go wrong. My efforts to restore proper operation consisted of
doing
the following:
$ ptxdist clean browser
$ ptxdist clean qt4
$ ptxdist clean root
then
$ ptxdist go
deleting the four "unwanted" .qmake.cache files in
build-host/qt-everywhere-opensource-src-4.6.3-build
build-host/qt-everywhere-opensource-src-4.6.3-build/config.test
build-target/qt-everywhere-opensource-src-4.6.3-build
build-target/qt-everywhere-opensource-src-4.6.3-build/config.test
then
$ ptxdist go
deleting folders
build-host/qt-everywhere-opensource-src-4.6.3-build
build-host/qt-everywhere-opensource-src-4.6.3-src
build-target/qt-everywhere-opensource-src-4.6.3-build
build-target/qt-everywhere-opensource-src-4.6.3-src
then
$ ptxdist go
A common error message was:
/home/davef/Pengutronix-6/OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/
platform-mini2440/sysroot-target/usr/lib/
libQtCore.a(qlibrary_unix.o): In function `qdlerror()':
qlibrary_unix.cpp:(.text+0x88): undefined reference to `dlerror'
.....
/opt/OSELAS.Toolchain-2011.03.0/arm-v4t-linux-gnueabi/
gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/lib/gcc/
arm-v4t-linux-gnueabi/4.5.2/../../../../arm-v4t-linux-gnueabi/bin/
ld: warning: creating a DT_TEXTREL in object.
collect2: ld returned 1 exit status
make[2]: Leaving directory `/home/davef/Pengutronix-6/
OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/build-target/
qt-everywhere-opensource-src-4.6.3-build/src/network'
make[1]: Leaving directory `/home/davef/Pengutronix-6/
OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/build-target/
qt-everywhere-opensource-src-4.6.3-build'
make[2]: *** [../../lib/libQtNetwork.so.4.6.3] Error 1
make[1]: *** [sub-network] Error 2
make: *** [/home/davef/Pengutronix-6/
OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/
state/qt4.compile] Error 2
davef@davef-desktop:~/Pengutronix-6/OSELAS.BSP-Pengutronix-Mini2440-2011.06.0$
I suspect this is possibly the first instance of a Qt library being
cross-compiled.
Next, I deleted OSELAS.BSP-Pengutronix-Mini2440-2011.06.0 and started
over again. This time I checked basic kernel operation and then added
Qt and the Qt options to support Arora. Having previously
cross-compiled
/demos/browser using the PTXdist toolchain I just dropped it's
binary into
/usr/bin and the program runs properly.
So, the question is how should one reclaim a BSP after it has
obviously been
corrupted because of failed attempts at cross-compiling Qt?
--
ptxdist mailing list
[email protected] <mailto:[email protected]>
--
--------------------------------------------------
Bart De Vos
Development Engineer
mailto:[email protected]
EIA Electronics
Vluchtenburgstraat 3
B-2630 Aartselaar (Belgium)
phone : +32(0)3 870 85 29
fax : +32(0)3 877 14 72
website : http://www.eia.be/
--------------------------------------------------
Basically, perfect development is impossible.
Development can be fast, good and cheap. Pick two!
--- Larry Wall
--------------------------------------------------
--
ptxdist mailing list
[email protected]
