Hello,
I have created the directory MACHTYPE in home directory in bin. The variable of my MACHTYPE is x86_64-linux-gnu. To check whether my executables are storing in the directory I have tried to make fixCr by going to the directory Downloads/kent/src/utils/fixcr and typed make. The fixCr program did not come to the x86_64-linux-gnu directory. It says this whenever I type make
cc -O -g -o /home/sabreena/bin/x86_64/fixCr fixCr.o ../../lib/x86_64/jkweb.a /usr/lib/x86_64-linux-gnu/libmysqlclient.a -ldl -lstdc++ -lrt -lpthread /usr/lib/x86_64-linux-gnu/libssl.a -lcrypto ../../htslib/libhts.a -lpng16 -lm -lz
/home/linuxbrew/.linuxbrew/bin/ld: cannot open output file /home/sabreena/bin/x86_64/fixCr: No such file or directory
collect2: error: ld returned 1 exit status
make: *** [../../inc/userApp.mk:31: /home/sabreena/bin/x86_64/fixCr] Error 1
Why the output file cannot be opened? What's wrong here?
Yes, I followed your advice and hence a long process took place. Now, it did not say the file cannot be opened but gave an another error.
collect2: error: ld returned 1 exit status make: *** [../../inc/userApp.mk:31: /home/sabreena/bin/x86_64/fixCr] Error 1
Why did this error come?
The relevant error message is the line above the output you gave, please give all the output.
This is the error message which came in loads, i just could provide a part of it due to the limitation of this text box..
How should i solve the error?
Hi, there might be a version mismatch or missing library. I anticipate that it may be very hard or impossible to fix. In general BLAT doesn't use a modern build system and is terribly awkward to build from source (sorry, Jim). So there might be no reasonable way of installing it that way. Instead, please try to install it via bioconda https://bioconda.github.io/recipes/ucsc-blat/README.html
I did not understand what you meant.. Could you please elaborate?
Sorry, but it does not really matter. I guess it will be nearly impossible to debug the problem using this forum. Please try the bioconda recipe first and see where this leads.
Actually I managed to find a fix for the same issue (undefined reference to WPACKET blabla) by installing a VM with Ubuntu 18.04 on it, if it can help you :)