Compiling issue for M1 Macbook Pro

[vijaychoyal26]

when compiling LAMMPS with a rosetta enabled terminal, getting the following error
Undefined symbols for architecture x86_64:
"_aenet_Rc_max", referenced from:
LAMMPS_NS::PairAenet::init_style() in pair_aenet.o
"_aenet_all_loaded", referenced from:
LAMMPS_NS::PairAenet::init_style() in pair_aenet.o
"_aenet_atomic_energy_and_forces", referenced from:
LAMMPS_NS::PairAenet::compute(int, int) in pair_aenet.o
"_aenet_final", referenced from:
LAMMPS_NS::PairAenet::~PairAenet() in pair_aenet.o
"_aenet_init", referenced from:
LAMMPS_NS::PairAenet::init_style() in pair_aenet.o
"_aenet_load_potential", referenced from:
LAMMPS_NS::PairAenet::init_style() in pair_aenet.o
ld: symbol(s) not found for architecture x86_64

I am using the exact same versions for aenet, lammps as those given on the GitHub tutorial (aenet-2.0.4 and lammps 4feb20). I switched to rosetta terminal since aenet was only able to compile on that terminal. Has anyone faced a similar problem and/or have a solution for the same?

[michaelstchen]

Unfortunately I do not have an M1 Mac to test the compilation procedure. I might be able to borrow an M1 Mac at some point next week to try reproducing things.

In the meantime, have you had the opportunity to try compiling on a different machine (one not using the newer M1 chip) following the same procedure and, if so, how did that go? From these errors my first guess is that there is an issue with linking to the aenet library files since all of the undefined symbols are variables or routines from aenet, but without more details or testing things out myself I cannot say for sure.

[vijaychoyal26]

Thanks for getting back to me. yes, I have tried the same procedure on a different machine (the github tutorial one itself), one running on an intel i7 cpu with ubuntu 20.04.2. On that the lammps aenet package works correctly, and I can run the water example provided on github. Additionally, I am trying to install the serial version using the gfortran_serial makefile (I did the sme on the linux machine as well). Thank you for your kind reply.

…

On Fri, 22 Oct 2021, 23:30 Michael Stephen Chen, ***@***.***> wrote: Unfortunately I do not have an M1 Mac to test the compilation procedure. I might be able to borrow an M1 Mac at some point next week to try reproducing things. In the meantime, have you had the opportunity to try compiling on a different machine (one not using the newer M1 chip) following the same procedure and, if so, how did that go? From these errors my first guess is that there is an issue with linking to the aenet library files since all of the undefined symbols are variables or routines from aenet, but without more details or testing things out myself I cannot say for sure. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIFNC7YCSH2FAU7EK2OFOFLUIGRCPANCNFSM5GPXGMKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.