KellenSunderland commented on issue #8073: Locate liblapack.a in /usr/lib64 URL: https://github.com/apache/incubator-mxnet/pull/8073#issuecomment-333482834 For Debian based distributions it should be in the linker search path already as it's the default location for 64bit libraries: https://wiki.debian.org/Multiarch/LibraryPathOverview On Amazon Linux (RHEL based) it seems to also be on the path: ```bash [ec2-user@ip-172-31-14-78 ~]$ gcc -Xlinker -v collect2 version 4.8.3 20140911 (Red Hat 4.8.3-9) /usr/bin/ld --build-id --no-add-needed --eh-frame-hdr --hash-style=gnu -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 /usr/lib/gcc/x86_64-amazon-linux/4.8.3/../../../../lib64/crt1.o /usr/lib/gcc/x86_64-amazon-linux/4.8.3/../../../../lib64/crti.o /usr/lib/gcc/x86_64-amazon-linux/4.8.3/crtbegin.o -L/usr/lib/gcc/x86_64-amazon-linux/4.8.3 -L/usr/lib/gcc/x86_64-amazon-linux/4.8.3/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-amazon-linux/4.8.3/../../.. -v -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-amazon-linux/4.8.3/crtend.o /usr/lib/gcc/x86_64-amazon-linux/4.8.3/../../../../lib64/crtn.o GNU ld version 2.23.52.0.1-55.65.amzn1 20130226 ``` Just thinking a little more about what we're doing here and, as a developer, I find this behaviour quite counter-intuitive. Currently I have the LAPACK flag turned on in the build configuration, I build a project successfully, and later at runtime I notice that in fact LAPACK wasn't linked. I then have to search through the source for references to the LAPACK variable to find that it is silently turned off without logging in the Makefile. This seems to be the case with LAPACK but with no other linked library, and I'm not sure what the cause for the inconsistent behaviour is here. I would actually prefer to get a linker error so that I know something is wrong. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
