PureBasic Forums - English

I am currently testing the 64-bit Fedora 13 vmplayer (vmware), I like the consistency and timeliness of the fedora, such as 64-bit libraries are installed in /usr/lib64 and those of 32-bit /usr/lib, this problem arises with purebasic 64 bit, it seems :roll: that the compiler searches for example lib 64-bit libstdc++ /usr/lib instead of /usr/lib64 :


- How to set purebasic 64 bit, it looks for the libs in /usr/lib64 instead of /usr/lib

Every other linux distribution developing group noticed that its better to symlink /usr/lib to /usr/lib64 instead of /usr/lib32.

I find that keeping /usr/lib for libraries 32-bit is more coherent and allows compatibility with 32-bit packages, the Fedora can also be installed without problems and the old packages can be used without the worries 32-bit programs in perfect consistency with the 64-bit programs, it makes me seem very logical ...


purebasic is what can change the path of access to libraries, would solve the problem ...

Well, apparently, is that the checkinstall script kidding me and misled since verified the presence of the libstdc + + lib in / usr / lib instead of / usr/lib64, he would still have the adapt to the 64-bit ...

so I installed the libraries need and purebasic run properly, but I have a problem when compiling with this message:



having said that I manage to compile the source code into executable directly but has not run under purebasic ...