Hi, Everyone;
I’m trying to build LIGGGHTS in Cygwin (and before anyone suggests otherwise - Yes, I need to do it in Cygwin, and other platforms won’t work for what I require). I’ve edited the makefile.cygwin and the .bashrc files and have overcome most of the problems associated with building the executable. However, after “make cygwin” runs for a while, I get the following errors and the build does not complete:
#C:\MSDEV\LIB -o …/lmp_cygwin
#c++: C:MSDEVLIB: No such file or directory
#make[1]: *** […/lmp_cygwin] Error 1
#make[1]: Leaving directory ‘/home/Steve/liggghts_1p1p10/src/Obj-cygwin’
#make: *** [cygwin] Error 2
Any help would be greatly appreciated.
Thanks in advance,
Stan
Hi, Everyone;
I'm trying to build LIGGGHTS in Cygwin (and before anyone suggests otherwise
- Yes, I need to do it in Cygwin, and other platforms won't work for what I
require). I've edited the makefile.cygwin and the .bashrc files and have
that is what everybody says. 
overcome most of the problems associated with building the executable.
However, after "make cygwin" runs for a while, I get the following errors
and the build does not complete:
#C:\MSDEV\LIB -o ../lmp_cygwin
#c++: C:MSDEVLIB: No such file or directory
this looks like you missed a -L somewhere when you edited your makefile.
axel.
Hi, Axel;
Thanks for responding. I’ll double-check the makefile.cygwin and make sure that the -L’s occur where they are supposed to. If I can’t make it work, would be be ok if I copy/pasted the key sections of my makefile.cygwin for liggghts up on the mailing list for some kind soul to glance at?
I’m perplexed, mostly because I successfully built lammps editing the same lines in its makefile.cygwin. I’m equally perplexed because the error message I received with building liggghts seems to reference something outside of the main cygwin folder I’ve been operating out of on my c-drive. All of my attempted builds have occured under c:\cygwin\etc,etc… The error says that it doesn’t like something to do with c:\MSDEV\LIB (which, I believe, has nothing to do with lammps and/or liggghts, and if it does, why can I build lammps successfully?).
Thanks,
Stan
Hi, Axel;
Thanks for responding. I'll double-check the makefile.cygwin and make sure
that the -L's occur where they are supposed to. If I can't make it work,
would be be ok if I copy/pasted the key sections of my makefile.cygwin for
liggghts up on the mailing list for some kind soul to glance at?
i think at this point, your best bet is to contact the LIGGGHTS author
directly. this looks like it is something relating to his modifications
to the lammps code. there have been some changes recently to
make the integration of packages more consistent and accommodate
additional requirements of packages that have most of their code
in external libraries. there may be some clashes because of that
and they are not always easy to spot if you only work on a limited
number of platforms.
is the requirement for cygwin a hard requirement, or is it only that
you have to produce a windows binary (serial or parallel?). one
interesting alternative could be the linux-to-mingw cross-compiler.
i am able to produce windows binaries on my fedora 12 box without
ever touching a windows machine (i test them with wine and the
occasional volunteer). the beauty of it is that i can still have the
familiar work and build environment.
cheers,
axel.
Hi, Axel;
Well, all I really need is a windows binary (parallel, if possible, but not necessary). However, I will be using liggghts for rock mechanics research where the sizes of the physical samples to be modeled might be better handled by an on-site supercomputer. This supercomputer uses LINUX, which is why I need to create binaries on my system and prove that it works before we request time on the supercomputers. The administrator for the big system is a bit touchy about building stuff on his precious machines; he’d rather us do it on our (expendable) systems.
I’ll definitely try contacting the liggghts author to see if this issue has been encountered before.
Thanks,
Stan
Hi, Axel;
Well, all I really need is a windows binary (parallel, if possible, but not
necessary). However, I will be using liggghts for rock mechanics research
where the sizes of the physical samples to be modeled might be better
handled by an on-site supercomputer. This supercomputer uses LINUX, which
is why I need to create binaries on my system and prove that it works before
we request time on the supercomputers. The administrator for the big system
is a bit touchy about building stuff on his precious machines; he'd rather
us do it on our (expendable) systems.
this is _totally_ stupid. what good is a machine, if people are not using it?
lammps is a user level application and does in no way need any administrative
privileges and thus should not be able to "ruin" any machine except by
deliberate denial of service attack against a weakness in the configuration
of the machine. furthermore LAMMPS has shown to scale very well and to
very large degrees. i have been able to scale (large) calculations up to
100,000 processor cores on the jaguar machine at ORNL.
the only words that come to my mind to express my opinion on this
kind of attitude towards users, i cannot write in public.
mind you, i do and have managed multiple machines for different groups
of users (i am in the process of piecing together a 100+ nodes machine
here at temple _right now_), so i do know the situation very well from both
sides of the fence.
I'll definitely try contacting the liggghts author to see if this issue has
been encountered before.
if some unreasonable sysadmin is the only reason that you have
to try to get a windows compile going, then you should rather have
that sysadmin "reprogrammed". contact me in private, if you need
help with that.
cheers,
axel.