you don't seem to have 'make' or 'qmake' in your PATH

Asha

Hi guys,

I am very new to this qt,

I am waiting for your replies...

Please suggest me....

Thankyou...

SGaist

Please show some patience. This forum is user driven. People answer here on a voluntary basis. They may also not live in the same time zone as you.

As for your issue, please post the complete configure line you used. Please past it here as text, having an image makes it difficult to read and test locally.

Also, what cross-compiler are you using ?
Did you clean up properly before restarting ?
Are you using an out of source build ?

Asha

@SGaist
Sorry for the hurry...

The configure line is:

./configure -platform linux-g++ -release -device linux-beagleboard-g++ -sysroot /home/beagle/BBB/sysroot -prefix /home/debian/Qt5ForBBB1 -hostprefix ~/Qt5ForBBB1 -device-option CROSS_COMPILE=/home/beagle/BBB/gcc-linario-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -nomake tests -nomake examples -no-opengl -opensource -confirm-license -reduce-exports -make libs -no-egl -no-eglfs -qt-zlib -qtlibpng -no-use-gold-linker -linuxfb -qt-libjpeg -no-openssl -no-cups -no-glib -no-iconv -nomake examples -nomake tools -nomake tests -no-pkg-config -skip qtdeclaritive -skip qtlocation -skip qtpurchasing -skip qtwayland -skip qtwebchannel -skip qtwebengine -skip qtwebsockets -skip qtwebview -skip qt webglplugin -skip qtandroidextras -skip qtgamepad -skip qtmacextras -skip qtwinextras -skip qtsensors -skip qtconnectivity -recheck-all -v

Cross compiler is : ARM

I cleaned using : "sudo apt-get clean"
is it correct or any other method to clean?

I am not understood about the last question,out of source build...

(I am not able to login qt forum in my laptop,so I am uploading the screenshots sorry for this).....

jsulm

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

I cleaned using : "sudo apt-get clean"

you need to clean the source tree, not apt:

make clean

Better is to do out of source builds: that just mean that you create a build directory, go to that directory and call configure from there.

mkdir build_qt
cd build_qt
../qt5_sourcecode/configure...

Asha

@jsulm

when I am giving the make clean

The result is:

make: *** No rule to make target 'clean'. Stop

Yes,I created the build directory qt-5.13 and calling ./configure there it self..

jsulm

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

Yes,I created the build directory qt-5.13 and calling ./configure there it self..

So, what happens now? Does configure succeed? Did you try to build?

Asha

@jsulm

I am not created now,I created at first only,and call the ./configure but getting that error.....

configuration is not succeed..

what about make clean...

jsulm

@Asha If you call ./configure then you're NOT doing out of source build!
Please read once more what I wrote before:

mkdir build_qt
cd build_qt
../qt5_sourcecode/configure...

Asha

@jsulm

shall I ask what is that ../qt5_sourcecode/configure....

jsulm

@Asha qt5_sourcecode is just a placeholder for the directory where you extracted Qt source code, replace it with the name of your Qt source code directory...
configure is what it is - configure command in Qt source code directory.

I explain this approach once more: you do NOT call configure inside the Qt source code directory, but from an empty build directory.

Asha

@jsulm

Yes,I extracted qt source code in my user directory(/home/beagle/)

After that I replaced it into a directory called qt-5.13(replaced via....mv qt-everywhere-src-5.13.1 ~/qt-5.13)

And calling the configure in this directory only.

Some more information here..

make --version
GNU Make 4.1
Built for x86_64-pc-linux-gnu

uname -srv
Linux 5.0.0-29-generic #31~18.04.1-Ubuntu

Which make
/usr/bin/make

echo $LD_LIBRARY_PATH
not displaying anything

jsulm · uname -srv Linux 5.0.0-29-generic #31~18.04.1-Ubuntu

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

After that I replaced it into a directory called qt-5.13(replaced via....mv qt-everywhere-src-5.13.1 ~/qt-5.13)

Again, this is not how it works!
You do NOT call configure from the source code directory for out of source builds, but from an empty directory!
Again:

# Create an empty directory:
mkdir build_qt
# Go to that empty directory:
cd build_qt
# Call configure from the Qt source code directory:
../qt5_sourcecode/configure...

Asha

@jsulm pwd is qt-5.13,here I need to create directory?if yes ,I created and tried getting

bash : ./configure : No such file or directory

please go through this link https://forum.qt.io/topic/106766/can-we-change-the-compiler-in-qmake/28 I followed this pdf...

jsulm

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

bash : ./configure : No such file or directory

Please read more carefully what I'm writing!
You need to use complete path (or relative) to configure!
That's why I wrote:

../qt5_sourcecode/configure

You can use absolute path instead of relative:

PATH_TO_YOUR_QT_SOURCE_DIRECTORY/configure

Asha

@jsulm

yes,I gave the hole path /home/beagle/qt-5.13/.configure

its starts configuring but not succeed...

After few minutes its stops with error

/home/beagle/qt-5.13/build_qt/qtbase/bin/qmake: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Asha

but libstdc++.so.6 library is present in my system...

location is:

/usr/arm-linux-gnueabihf/lib/libstdc++.so.6

jsulm

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

is present in my system

It needs to be present in your sysroot since you're cross compiling

Asha

@jsulm yes this library is present in sysroot also..

here is the attachement

Asha

when I gave the command below

qmake --version

The result is:

Qmake version 3.1
using Qt version 5.9.5 in /usr/lib/x86_64-linux-gnu

Is this any issue?

jsulm

@Asha said in you don't seem to have 'make' or 'qmake' in your PATH:

Is this any issue?

No, this is qmake from Qt delivered by Ubuntu.
qmake for your cross compiled Qt will be built when you cross compile Qt, but I don't know why you get that libstdc++ error.