On 6/4/20 5:29 PM, Joe Locash wrote:
Doug,
There is no need to apologize. I'm happy to help out in any way. I
didn't quote your reply but I'm curious about llvm playing a role in
this. I also build it very early. The book states if LLVM is compiled
with clang support then ncftp will use
that. Obviously it didn't in my case. Thoughts?
-Joe
I'm curious as well. If you check the configure output, is yours doing
something like this?:
Making ncftp-3.2.6-src
Thu 04 Jun 2020 09:46:36 AM CDT
creating cache ./config.cache
checking if you set and exported the environment variable CC... no
(configure will try to locate a suitable C compiler)
checking for environment variable CFLAGS... no (we will choose a default
set for you)
checking for environment variable CPPFLAGS... no
checking for environment variable LDFLAGS... no
checking for environment variable LIBS... no
checking for clang C compiler... /usr/bin/clang
checking if CC should now be set... /usr/bin/clang
checking for gcc... /usr/bin/clang
checking whether the C compiler (/usr/bin/clang ) works... yes
checking whether the C compiler (/usr/bin/clang ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether /usr/bin/clang accepts -g... yes
checking version of C library... glibc2.31
I'm curious as to why it redefines 'gcc' to 'clang'.
I think LLVM is package #20 for me. It's easier to get that one done
while working on other things :)
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
