[Qt5]Building Qt5 on Ubuntu 12.04[solved]

akrynski

@Build steps – Linux XCB (Ubuntu 12.04)

Install dependencies of Qt 4 “sudo apt-get build-dep libqt4-dev”
Install additional dependencies “sudo apt-get install gperf bison” (needed to compile QtWebkit)
Install xcb dependencies “sudo apt-get install libxcb1 libxcb1-dev libx11-xcb1 libx11-xcb-dev libxcb-keysyms1 libxcb-keysyms1-dev libxcb-image0 libxcb-image0-dev libxcb-shm0 libxcb-shm0-dev libxcb-icccm4 libxcb-icccm4-dev libxcb-sync0 libxcb-sync0-dev libxcb-xfixes0-dev libxrender-dev libxcb-shape0-dev”
cd to the directory where you extracted the tarball and run ./configure (with the options suggested above)
Run “./build” and wait for some time. If you have multiple cores, use ./build -j <number of cores> to speed up the build process

@
DONE!

Required build tools:
@Required build tools

Perl 5.8 or later
Python 2.7 or later@

Available build tools:
@VPCEC3C5E:~$ perl -V
Summary of my perl5 (revision 5 version 14 subversion 2) configuration:@

I have Python 2.7.3 (default, Apr 20 2012, 22:39:59)

And configure error:
@VPCEC3C5E:~/qt-everywhere$ ./configure
bash: ./configure: /usr/bin/perl^M: zły interpreter: Nie ma takiego pliku ani katalogu
(it means: bad interpreter: there is no such file nor directory)@

Is there any way to build it? Where is an error? Why ^M is added to command line?
Dos2unix is a good solution, but why? Why me? Building instructions for linux? Ha, ha, ha! ;)

Greets :D
A.K.

william

It seems that you use the zip archive format which is for windows platform. Use the bz2 or gz format instead.

Skylar

I use to build QT5 from git directly on ubuntu 11.10 and 12.04, all running smoothly.

http://qt-project.org/wiki/Building-Qt-5-from-Git

akrynski

[quote author="william" date="1342663151"]It seems that you use the zip archive format which is for windows platform. Use the bz2 or gz format instead.[/quote]

Yes, I do. I even didn't know there is any difference. And IMO it shouldn't be.

TNX guys.

tobias.hunger

Maybe it is a localization issue where the script expects english output and gets whatever language you are using.

try running "LANG=C LC_ALL=C ./configure" to force the non-localized strings to appear.