I have made (compiled) msi2lmp.exe file in the tools folder in lammps software to make a data file for lammps.
I use this file and the corresponding command like this:
…/msi2lmp.exe polymer -class II -frc pcff > data.polymer
However, I encounter this error:
in Mac terminal: msi2lmp.exe: command not found
in linux terminal: ./msi2lmp.exe: cannot execute binary file
It seems the problem is related to msi2lmp.exe.
What is the problem?
I have made (compiled) msi2lmp.exe file in the tools folder in lammps
software to make a data file for lammps.
which version? what platform? what compiler? you left out all the
essential information here as it is explained in the mail list posting
guidelines. tsk, tsk, tsk.
I use this file and the corresponding command like this:
.../msi2lmp.exe polymer -class II -frc pcff > data.polymerHowever, I encounter this error:
in Mac terminal: msi2lmp.exe: command not found
in linux terminal: ./msi2lmp.exe: cannot execute binary fileIt seems the problem is related to msi2lmp.exe.
no, it doesn't. it seems to be a case of PEBCAC.
What is the problem?
in the first case you seem to be trying to call an executable that is
located in a directory not listed in $PATH (in other words, you did *not*
type ./msi2lmp.exe .... as you claim)
in the second case, you seem to be executing a binary that was not compiled
for that particular OS.
axel.
Sorry for not mentioning some information. I added the essential info.
I tried to make the file both in linux as well in mac terminals. The version of lammps I used is 10 May 2014. Also tried it with stable version and development versions.
I copied all the essential files (.car and .mdf and pcff.frc and msi2lmp.exe files) in the same folder and executed the command:
…/msi2lmp.exe polymer -class II -frc pcff
How can I make a file for a specific OS, i.e. Windowns, Mac or Linux? I used just the simple command “make” and a .exe file was made. Please help if I have done it wrongly.
I also used the msi2lmp.exe file I made in linux, in cmd in a windows 8 OS and used the same command:
…/msi2lmp.exe polymer -class II -frc pcff
The following message appeared on the screen:
“Program too big to fit in memory”
Sorry for not mentioning some information. I added the essential info.
I use this file and the corresponding command like this:
.../msi2lmp.exe polymer -class II -frc pcff > data.polymer
However, I encounter this error:
in Mac terminal: msi2lmp.exe: command not found
in linux terminal: ./msi2lmp.exe: cannot execute binary fileIt seems the problem is related to msi2lmp.exe.
no, it doesn't. it seems to be a case of PEBCAC.
What is the problem?
in the first case you seem to be trying to call an executable that is
located in a directory not listed in $PATH (in other words, you did *not*
type ./msi2lmp.exe .... as you claim)I copied all the essential files (.car and .mdf and pcff.frc and
msi2lmp.exe files) in the same folder and executed the command:
.../msi2lmp.exe polymer -class II -frc pcff
but this command line is inconsistent with the other two options you gave
*and* both error messages. thus at this point, i don't have any idea what
it is exactly that you did. it works for me.
in the second case, you seem to be executing a binary that was not
compiled for that particular OS.How can I make a file for a specific OS, i.e. Windowns, Mac or Linux? I
used just the simple command "make" and a .exe file was made.
in the most simple case, you have to compile on the platform that you want
to run on. however, you have to have a working compiler environment. the
latter i cannot judge from remote. as stated above, it works for me (and
for a lot of other people).
Please help if I have done it wrongly.
unless you provide a concise, consistent and complete description of what
you did exactly, nobody can say.
it may be simpler, if you use a precompiled executable.
I also used the msi2lmp.exe file I made in linux, in cmd in a windows 8 OS
and used the same command:
.../msi2lmp.exe polymer -class II -frc pcff
that *cannot* work.
The following message appeared on the screen:
"Program too big to fit in memory"
leave it to windows to provide a meaningless error message...
axel.