[ptxdist] Qt and mini2440 BSP
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 ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
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 dave_fest...@hotmail.com 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 ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
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 dave_fest...@hotmail.com mailto:dave_fest...@hotmail.com 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 ptxdist@pengutronix.de mailto:ptxdist@pengutronix.de -- -- Bart De Vos Development Engineer mailto:bart.de...@eia.be 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 ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
Bart, Thank you for the example clean step. I'll give it a try next time I get into trouble! MC, Arora won't run reliably on a 64M machine, so I use /demo/browser instead. -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
Bart, Can not find a qt4.make file, but get the general idea. There are a lot of files in the /state directory that appear to control the build/install process. Dave -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
Dave wrote: Can not find a qt4.make file, but get the general idea. There are a lot of files in the /state directory that appear to control the build/install process. Take a look into your PTXdist installation directory: In rules/qt4.make you will find the mentioned file. To modify it, just copy it to your local project's rules/ directory and modify it. PTXdist will always use the local one instead of the global one. jbe -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | http://www.pengutronix.de/ | -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
Juergen, Found it after reading your explanation about Projectroot in my other posting! Thanks, Dave -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] strange memory errors with OSELAS.Toolchain-1.99.3.6 (i386 architecture)
Hallo,
I hope this is the correct mailing list. I have some strange memory errors.
There are some program functions that cause not reproducible segmentation
faults. I used the memcheck tool to check what happens in these functions:
$valgrind --tool=memcheck --leak-check=full --show-reachable=yes
--show-emwarns=yes --smc-check=all -v ./app
There is a small sample program at the end, where I use log4cpp to reproduce the
error.
Is there a special toolchain/gcc/glib flag or option that has to be set? When
the program is not cross compiled and is running under Ubuntu 10.10, there are
no errors/warnings/segmention faults.
Best regards,
Christian Muellerleile
Valgrind (3.5.0) memcheck output:
[..]
==1195== Emulation warning: unsupported action:
==1195== Selection of non-80-bit x87 FP precision
==1195==at 0x81979DD:
==1195==at 0x81A4069:
log4cpp::PatternLayout::setConversionPattern(std::string const) (in
/usr/bin/hexapod/hexfirmware_debug)
[..]
#include string
#include log4cpp/Category.hh
#include log4cpp/PatternLayout.hh
#include log4cpp/PropertyConfigurator.hh
#include log4cpp/FileAppender.hh
int main()
{
log4cpp::Appender* dapp = new
log4cpp::FileAppender(DEFAULT_LOGGER_APPENDER,
fileno(stdout));
log4cpp::PatternLayout* slayout = new log4cpp::PatternLayout();
slayout-setConversionPattern( %r [%t] %-6p %c %x: %m%n );
dapp-setLayout(slayout);
log4cpp::Category logger =
log4cpp::Category::getInstance(DEFAULT_LOGGER);
logger.setAdditivity( false );
logger.setAppender(dapp);
logger.setPriority((int)log4cpp::Priority::DEBUG);
struct tm *today;
time_t ltime;
time( ltime );
today = gmtime( ltime );
char szTime[200];
strftime( szTime, 199, %H:%M:%S - %A, %B %d, %Y (GMT), today );
log4cpp::Priority::PriorityLevel level = log4cpp::Priority::INFO;
logger.log((int)level, szTime);
return 0;
}
--
ptxdist mailing list
ptxdist@pengutronix.de
[ptxdist] Error getting host packages
Hi there, PTXdist fails to get host packages and ends with: error: empty parameter to 'ptxd_make_get' that's because we expand arguments to ptxd_make_get this way: ptxd_make_get $($(strip $(1))_SOURCE) $($(strip $(1))_URL) see rules/post/ptxd_make_world_get.make Here for example QT4_HOST_URL is undefined and build fails. What should suggested fix look like? Thanks, ladis -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] USB mouse with Qt app and touchscreen
Following this tutorial: http://www.armadeus.com/wiki/index.php?title=Qt/Embedded#Installation With a previous build of Qt/embedded I managed to get the USB mouse working in conjunction with the touchscreen by exporting this line, before using the USB mouse: export QWS_MOUSE_PROTO=MouseMan:/dev/input/mouse1 Tslib:/dev/input/touchscreen0 With Qt built by OSELAS.BSP-Pengutronix-Mini2440-2011.06.0 I determined that the USB mouse was now /dev/input/event3 and the touchscreen /dev/input/event1, so I changed the line to: export QWS_MOUSE_PROTO=MouseMan:/dev/input/event3 Tslib:/dev/input/event1 The touchscreen continues to work, but I can not any response from the mouse. Does MouseMan expect the mouse input to be /mouse (as per the tutorial) or should /event3 still be a valid input parameter? Thank you. Dave -- ptxdist mailing list ptxdist@pengutronix.de
