SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I'm testing qtCreator with building a simple "Hello world". I run Slackware current with qt5+qtCreatr from Slackbuilds. When building "HelloWorld" i have some error messages.
Quote:
skipping incompatible /usr/X11R6/lib/libthread.so when searching for -lpthread
skipping incompatible /usr/X11R6/lib/libthread.a when searching for -lpthread
skipping incompatible /usr/X11R6/lib/libstdc++ when searching for -lstdc++
skipping incompatible /usr/X11R6/lib/libm.so when searching for -lm
skipping incompatible /usr/X11R6/lib/libm.a when searching for -lm
skipping incompatible /usr/X11R6/lib/libgcc_s.so when searching for -lgcc_s
skipping incompatible /usr/X11R6/lib/libc.so when searching for -lc
skipping incompatible /usr/X11R6/lib/libc.a when searching for -lc
skipping incompatible /usr/X11R6/lib/libgcc_s.so when searching for -lgcc_s
I understand that is relating to compiler, but don't know how to resolve the problem
That looks very much like you're running a multilib system in which shared library objects are being searched for in /usr/lib rather than /usr/lib64. I think you'll have to revisit your building of qt5 and/or qt-creator (which work great here on a pure 64bit system).
Those are not errors, but messages resulting from your compiliation on a multilib computer. The linker should have found the correct 64-bit libraries after mentioning that it skipped the 32-bit libraries.
When using sbopkg, there are some problems of linkin libraries sometimes. with LDFAGS to lib64 this is resolved. Must we always put the LDFLAGS when building a package?
Are those "skipping ..." messages emitted when building your qt-creator package or when you are compiling an application (the "Hello world" you mention) from within qt-creator?
Discussion about LDFLAGS in sbopkg doesn't seem relevant to a Hello World project within qt-creator.
On the other hand I don't believe LDFLAGS needs to be set to build qt-creator itself either; last night I built qt-creator3 in a 14.1 multilib partition with no LDFLAGS set. I have searched the log file of the build and can find no "skipping ..." messages at all. It runs perfectly as far as I can see and a small test project (a window with four tabs) builds and runs with no errors, no warnings, no "skipping ..." messages.
In any case its unclear why /usr/lib is being searched in the first place (although as Alien Bob has pointed out, the "skipping ..." messages are informative rather than error messages). Perhaps its because you're building in an environment in which you've already run /etc/profile.d/32dev.sh (or it was run automatically from ~/.bashrc, ~/.bash_profile etc.) - I think that would be a mistake. Do your building in a "clean" environment.
Problem of flag hapen for some packages, not all time. I rebuild qt5 and t-creator with LDFLAGS and i reopen my test application on qt-creator and no warnings.
But now that you call me about /etc/profile.d/32dev.sh, i see that refers to /usr/lib directory. here are some lines
Quote:
# Modify the compilation/linking environment:
export PATH="/usr/bin/32:/usr/lib/qt/bin:$PATH"
# Change the shell prompt to make it clear that we are in 32bit mode:
PS1='\u@\h (32bit):\w\$ '
This is done from the build, but i am on 64bits current. I don't think that is comming from from bashrc. so this is strange
OK, I understand why. In fact this script is there if we compile 32-bit programs. It was all beast. Regarding Sbo and packages, I just try another tool called slpkg that some must surely know. And I must say that it has me completely amazed. no need to put flags, we choose what repository is used, and can even override slackpkg. Question dependencies, it rebuilds everything in a way completely clean. It is for me the Swiss army knife. Tell me if I tell ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.