-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR Makefile:123 OpenBLAS: Detecting CPU failed. Please set TARGET explicitly, e.g. make TARGET=your_cpu_target #983
Comments
N3520 appears to belong to the "Bay Trail" core series of "ATOM" type CPU, so please try building with "make TARGET=ATOM". |
sorry, had a problem cause first I thought that "cat/proc/cpuinfo" would mean a path I could not find but than I copied the string and while inserting I recogniced the "SPACE" and that this is a COMMAND processor : 0 Sorry, but I am completly "Linux" blind / newbie and I just can imagine that your git clone https://github.com/torch/distro.git ~/torch --recursive I think the error occured by the last step so it might be necessary to change the last script / batchfile install.sh |
Here is what I found in the torch install.sh regarding openblas *if [[ That maybe environment variable $prefix is a few line later used here with a make command cmake .. -DCMAKE_INSTALL_PREFIX="${PREFIX}" -DCMAKE_BUILD_TYPE=Release -DWITH$$ I hope that might help to find a workaround. I just want to try to cholorize 100 year old photographs with this and therefore I learned to install vmware player, only to finally start torch and siggraph to get colored pics from the world exhibition chicago 1892 Long journey till now - at least for me Thanks |
NO, it happened earlier while executing bash install-deps
And here is the echo of that script and the way to that error
Hope that will help to find where I have to insert / change what. Thanks a lot |
Alright then, try adding the "TARGET=ATOM" to the end of the line |
Hey, I edited the install-deps FILE here in the last line
BUT: I still got the same error Or do I have to remove the quotations to TARGET=ATOM? |
Yes, sorry for that - no quotation marks around the TARGET=ATOM |
Sorry, even with no quotation marks I still got the same error Just checked it line by line - error is still the same |
In that function there is question for processors = 1 So I was wondering why I have to put that "Arguments" not into the first option cause I remembered that the ubuntu settings in my VM Player were 1 There I found If I click on processor then I get more information like Number of cores 1 I did not change anything here - it's just the ubuntu iso image I downloaded. If TARGET=ATOM shall work in my environment doesn't the TARGET=ATOM in the 2 line here for processors = 1 ?
Shall I try that? |
Now the system is still running but I see a lot of messages I did not see before. Seems to me that the script is using the first line after if and not the ELSE
Maybe I have to move the TARGET=ATOM in the line ? |
I canceled the previous run .
Right now it is running again and I will let it run through .... and see what happens many lines of this are still running - just marked while still running , then copy ... to paste it here.
|
Yep. Did not really think through about the implications of the VM, i.e. that you might have just one core assigned to it, and only edited what I wrote earlier instead of creating a new message so you probably did not see it in time. Think it will run to completion now that you found out yourself what needed to be changed. (I'll see if I get around to creating a patch to recognize intel cpu code 55 - 37 in hexadecimal meaning extended model 3, model 7 - similar to 52eba81 ) |
I got tons of lines on the screens - some warnings ... it is running and running BUT: Is it really only a question of cores that if if [ $(getconf _NPROCESSORS_ONLN) == 1 ]; then Then I will change my ubuntu settings from 1 core to 2 cores and see what will happen - maybe / hopefully without all these warnings |
The tons of lines of output are harmless - OpenBLAS is quite a big library and this is mostly just the normal feedback from compiling each of the many source files. You may get an occasional warning about some unused local variable, and towards the end of the build process it will also build and run some automated tests to check its accuracy, but as long as it does not terminate with an error message everything should be alright. |
Hey, finally I stopped the 1 processor virtual ubuntu machine and started a new run as 2 processor machine That is still running ... Let's wait and see ... at least much better than the last 2 or 3 days regarding progress and feelings. |
DID IT but what does this mean - appeared shortly before the end
|
Seems the build went through correctly (the "make install" step is a few lines below the one we edited and will probably not have generated any output except perhaps asking for the system password), but the script still recognized only a single core. Depending on what torch and/or that siggraph code does, a single-threaded openblas may actually be all you need. |
I have a up to date WIN 10 system with
VM Player 12 running on an INTEL 4 CORE CPU N3520
With both iso of ubuntu 12 and mint 18 I got that sam ERROR 123 while installing torch 7 ....
First I thougt it was a torch problem and in the torch readme was nothing to be found about 123 error
Then I found a reference here in the issues with a solution using the version 0.2.9.rc2
But that regards a mac pro problem and I have windows 10 and Intel CPU.
Tested it on 2 machines with both ISO Files.
How can I set that CPU Target to what value?
Thanks a lot
The text was updated successfully, but these errors were encountered: