llvm dev - Jan 2013 - [LLVMdev] Failure building llvm/clang from source using binary clang package on Mageia 2

On 01/07/2013 08:39 AM, Dmitri Gribenko wrote:
> On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener
> <eldlistmailingz at tropicsoft.com> wrote:
>> On Mageia 2 I have installed the binary clang package clang3.0-7. When
I
>> tried to build the latest llvm/clang from source using this binary
clang
>> I get this error:
>>
>> 1) In file included from
>> /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30:
>> /home/mgeldiener/vcs/llvm/lib/Support/Unix/Signals.inc:32:10: fatal
>> error: 'cxxabi.h' file not found
>> #include <cxxabi.h>
>>          ^
>> llvm[1]: Compiling Statistic.cpp for Debug+Asserts build
>> 1 error generated.
>> gmake[1]: ***
>> [/home/mgeldiener/dev/clang/build/lib/Support/Debug+Asserts/Signals.o]
>> Error 1
>> gmake[1]: *** Waiting for unfinished jobs....
>> gmake[1]: Leaving directory
`/home/mgeldiener/dev/clang/build/lib/Support'
>> gmake: *** [all] Error 1
>>
>> If I build with gcc, there are no problems.
>
> Hello Edward,
>
> Here's a patch for ./configure that should detect and reject a broken
> clang in your cases.  Could you please apply and test on all platforms
> that you recently sent bug reports about?  You should see a clear
> error from ./configure that the selected compiler is broken.
After applying your patch on Mageia 2 and invoking llvm's configure:

Using clang 3.0 I get:

"checking whether clang works... no
configure: error: Selected compiler could not find or parse C++ standard
library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."

Using gcc, there is no error.

After applying your patch on Fedora 17 and invoking llvm's configure:

Using clang 3.0 I get:

"checking whether clang works... no
configure: error: Selected compiler could not find or parse C++ standard 
library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."

Using gcc, there is no error.

After applying your patch on Suse 12.2 and invoking llvm's configure:

Using clang 3.1, which has previously worked, there is no error.

So it looks to me, based on my tests, that your patch is successful. I 
look forward to this update in llvm on subversion. Thanks for your help 
on this matter. I will report the broken clang binary installation to 
Mageia 2 and Fedora 17.

On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener
<eldlistmailingz at tropicsoft.com> wrote:
> After applying your patch on Mageia 2 and invoking llvm's configure:
>
> Using clang 3.0 I get:
>
> "checking whether clang works... no
> configure: error: Selected compiler could not find or parse C++ standard
> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>
> Using gcc, there is no error.
>
> After applying your patch on Fedora 17 and invoking llvm's configure:
>
> Using clang 3.0 I get:
>
> "checking whether clang works... no
> configure: error: Selected compiler could not find or parse C++ standard
> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>
> Using gcc, there is no error.
>
> After applying your patch on Suse 12.2 and invoking llvm's configure:
>
> Using clang 3.1, which has previously worked, there is no error.
>
> So it looks to me, based on my tests, that your patch is successful. I look
> forward to this update in llvm on subversion.
I've committed a slightly different variant of this patch r171975.

Thank you for testing!

Dmitri

-- 
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at
gmail.com>*/

On 01/09/2013 10:37 AM, Dmitri Gribenko wrote:
> On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener
> <eldlistmailingz at tropicsoft.com> wrote:
>> After applying your patch on Mageia 2 and invoking llvm's
configure:
>>
>> Using clang 3.0 I get:
>>
>> "checking whether clang works... no
>> configure: error: Selected compiler could not find or parse C++
standard
>> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>>
>> Using gcc, there is no error.
>>
>> After applying your patch on Fedora 17 and invoking llvm's
configure:
>>
>> Using clang 3.0 I get:
>>
>> "checking whether clang works... no
>> configure: error: Selected compiler could not find or parse C++
standard
>> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>>
>> Using gcc, there is no error.
>>
>> After applying your patch on Suse 12.2 and invoking llvm's
configure:
>>
>> Using clang 3.1, which has previously worked, there is no error.
>>
>> So it looks to me, based on my tests, that your patch is successful. I
look
>> forward to this update in llvm on subversion.
>
> I've committed a slightly different variant of this patch r171975.
>
> Thank you for testing!
Glad to do it. Thanks for addressing this area.

On 01/09/2013 10:37 AM, Dmitri Gribenko wrote:
> On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener
> <eldlistmailingz at tropicsoft.com>  wrote:
>> After applying your patch on Mageia 2 and invoking llvm's
configure:
>>
>> Using clang 3.0 I get:
>>
>> "checking whether clang works... no
>> configure: error: Selected compiler could not find or parse C++
standard
>> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>>
>> Using gcc, there is no error.
>>
>> After applying your patch on Fedora 17 and invoking llvm's
configure:
>>
>> Using clang 3.0 I get:
>>
>> "checking whether clang works... no
>> configure: error: Selected compiler could not find or parse C++
standard
>> library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure
..."
>>
>> Using gcc, there is no error.
>>
>> After applying your patch on Suse 12.2 and invoking llvm's
configure:
>>
>> Using clang 3.1, which has previously worked, there is no error.
>>
>> So it looks to me, based on my tests, that your patch is successful. I
look
>> forward to this update in llvm on subversion.
>
> I've committed a slightly different variant of this patch r171975.
>
> Thank you for testing!
Unfortunately, after an attempt to use the latest 'configure' update on 
CentOS 6.3 I think your version may be slightly flawed.

I had been able to build clang from source on CentOS 6.3 using clang 
2.8-14 that is distributed as a binary. After your update, however, when 
I run llvm/configure I receive:

checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether clang++ accepts -g... yes
checking how to run the C preprocessor... clang -E
checking whether clang works... no
configure: error: Selected compiler could not find or parse C++ standard 
library headers.  Rerun with CC=c-compiler CXX=c++-compiler ./configure ...

When I run 'clang -v -fsyntax-only -x c++ /dev/null' I get:

"clang version 2.8 (branches/release_28)
Target: x86_64-redhat-linux-gnu
Thread model: posix
  "/usr/bin/clang" -cc1 -triple x86_64-redhat-linux-gnu -fsyntax-only 
-disable-free -disable-llvm-verifier -main-file-name null 
-mrelocation-model static -mdisable-fp-elim -mconstructor-aliases 
-munwind-tables -target-cpu x86-64 -target-linker-version 2.20.51.0.2 -v 
-resource-dir /usr/lib/clang/2.8 -ferror-limit 19 -fmessage-length 144 
-fexceptions -fgnu-runtime -fdiagnostics-show-option -fcolor-diagnostics 
-x c++ /dev/null
clang -cc1 version 2.8 based upon llvm 2.8 hosted on x86_64-redhat-linux-gnu
#include "..." search starts here:
#include <...> search starts here:
  /usr/include/c++/4.4.4
  /usr/include/c++/4.4.4/x86_64-redhat-linux
  /usr/include/c++/4.4.4/backward
  /usr/local/include
  /usr/lib/clang/2.8/include
  /usr/include
  /usr/lib/gcc/x86_64-redhat-linux/4.4.4/include
End of search list."

It looks to me that clang 2.8-14 does indeed find the necessary header 
files. Yet you are rejecting it. Also it did build clang successfully 
before your update.

Finally when I ran 'gmake -j4' and the llvm/configure fails, the
'gmake'
does not appear to ever end even if it prints out nothing further to the 
console screen.