From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4127 Path: news.gmane.org!not-for-mail From: Richard Pennington Newsgroups: gmane.linux.lib.musl.general Subject: ELLCC has self hosted. Date: Fri, 18 Oct 2013 18:02:36 -0500 Message-ID: <5261BE0C.2000904@pennware.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------070908050807090604020703" X-Trace: ger.gmane.org 1382137761 19607 80.91.229.3 (18 Oct 2013 23:09:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Oct 2013 23:09:21 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4131-gllmg-musl=m.gmane.org@lists.openwall.com Sat Oct 19 01:09:26 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VXJAZ-0005bH-9h for gllmg-musl@plane.gmane.org; Sat, 19 Oct 2013 01:09:23 +0200 Original-Received: (qmail 13732 invoked by uid 550); 18 Oct 2013 23:09:21 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 13721 invoked from network); 18 Oct 2013 23:09:21 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Xref: news.gmane.org gmane.linux.lib.musl.general:4127 Archived-At: This is a multi-part message in MIME format. --------------070908050807090604020703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit The clang/LLVM based ELLCC project (http://ellcc.org), after having reached a huge milestone (http://ellcc.org/blog/?p=231) has now successfully compiled itself. The steps were: 1. Use gcc to build the compiler with Linux standard libraries. 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, and compiler-rt 3. Use the newly built compiler to build itself again. One interesting side note: The compiler was 12MB smaller after it built itself. ct-fw-88 ellcc 622 % size */Release+Asserts/bin/ecc text data bss dec hex filename 52415858 2152024 84768 54652650 341eeea llvm-build/Release+Asserts/bin/ecc 40222706 2117136 135416 42475258 2881efa llvm-build-self/Release+Asserts/bin/ecc Even more interesting, it was compiled statically. No dynamic libraries needed: ct-fw-88 ellcc 623 % ldd */Release+Asserts/bin/ecc llvm-build/Release+Asserts/bin/ecc: linux-vdso.so.1 => (0x00007fff2ffff000) libz.so.1 => /lib64/libz.so.1 (0x00007facd87e1000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007facd85c4000) libncurses.so.5 => /lib64/libncurses.so.5 (0x00007facd837c000) librt.so.1 => /lib64/librt.so.1 (0x00007facd8173000) libdl.so.2 => /lib64/libdl.so.2 (0x00007facd7f6f000) libstdc++.so.6 => /home/de023789/gnulocal/lib64/libstdc++.so.6 (0x00007facd7c6e000) libm.so.6 => /lib64/libm.so.6 (0x00007facd7a18000) libgcc_s.so.1 => /home/de023789/gnulocal/lib64/libgcc_s.so.1 (0x00007facd7803000) libc.so.6 => /lib64/libc.so.6 (0x00007facd74a5000) /lib64/ld-linux-x86-64.so.2 (0x00007facd89f7000) llvm-build-self/Release+Asserts/bin/ecc: not a dynamic executable ct-fw-88 ellcc 624 % That is very cool. -Rich --------------070908050807090604020703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit The clang/LLVM based ELLCC project (http://ellcc.org), after having reached a huge milestone (http://ellcc.org/blog/?p=231) has now successfully compiled itself.

The steps were:
1. Use gcc to build the compiler with Linux standard libraries.
2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, and compiler-rt
3. Use the newly built compiler to build itself again.

One interesting side note: The compiler was 12MB smaller after it built itself.

ct-fw-88 ellcc 622 % size */Release+Asserts/bin/ecc

text data bss dec hex filename

52415858 2152024 84768 54652650 341eeea llvm-build/Release+Asserts/bin/ecc

40222706 2117136 135416 42475258 2881efa llvm-build-self/Release+Asserts/bin/ecc

Even more interesting, it was compiled statically. No dynamic libraries needed:

ct-fw-88 ellcc 623 % ldd */Release+Asserts/bin/ecc

llvm-build/Release+Asserts/bin/ecc:

linux-vdso.so.1 => (0x00007fff2ffff000)

libz.so.1 => /lib64/libz.so.1 (0x00007facd87e1000)

libpthread.so.0 => /lib64/libpthread.so.0 (0x00007facd85c4000)

libncurses.so.5 => /lib64/libncurses.so.5 (0x00007facd837c000)

librt.so.1 => /lib64/librt.so.1 (0x00007facd8173000)

libdl.so.2 => /lib64/libdl.so.2 (0x00007facd7f6f000)

libstdc++.so.6 => /home/de023789/gnulocal/lib64/libstdc++.so.6 (0x00007facd7c6e000)

libm.so.6 => /lib64/libm.so.6 (0x00007facd7a18000)

libgcc_s.so.1 => /home/de023789/gnulocal/lib64/libgcc_s.so.1 (0x00007facd7803000)

libc.so.6 => /lib64/libc.so.6 (0x00007facd74a5000)

/lib64/ld-linux-x86-64.so.2 (0x00007facd89f7000)

llvm-build-self/Release+Asserts/bin/ecc:

not a dynamic executable

ct-fw-88 ellcc 624 %

That is very cool.

-Rich

--------------070908050807090604020703-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4134 Path: news.gmane.org!not-for-mail From: agent Newsgroups: gmane.linux.lib.musl.general Subject: Re: ELLCC has self hosted. Date: Sun, 20 Oct 2013 22:49:59 +0600 Message-ID: <526409B7.3090607@gmail.com> References: <5261BE0C.2000904@pennware.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------090600000903090203080203" X-Trace: ger.gmane.org 1382287974 5566 80.91.229.3 (20 Oct 2013 16:52:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2013 16:52:54 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4138-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 20 18:53:00 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VXwFP-0006WE-JA for gllmg-musl@plane.gmane.org; Sun, 20 Oct 2013 18:52:59 +0200 Original-Received: (qmail 23725 invoked by uid 550); 20 Oct 2013 16:52:59 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 23709 invoked from network); 20 Oct 2013 16:52:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=JMigNIUW8lrAEP9/R24QvQYZgMdS2gGfF5ltYH059Jk=; b=o6NZA6h0GpkeoZMkKZpTt78wK7tXszDQQrgL5tu2sJFSvwCjOtvhfVpZMsMmfU1kV8 ndgXWdp+A1iGQElAQfekMLHQaSg+bFnPoDpCEP2PebqxFD8RZESC+Tzmgbm48hTYC3oN w7mqhuAbHnsdxtallgum7WFi5t9L2XrAjpblLumEEQsN7UbWQJ6/miiHtvWr/7ZMj5Xi kYp+PDizROxJd8MZXP3T3ziTyfOTl5BfCNpLImOvikl1CTfZlgTPDxJ2yvuOG6wyRgIj wOagcqydqlrJgxEa0xSTQ+ysQOv2G7yz5aDUtT5KCZ40E0+FxPRSjnGqAF8PLJ44+4Ma aAWw== X-Received: by 10.112.170.134 with SMTP id am6mr56909lbc.61.1382287967115; Sun, 20 Oct 2013 09:52:47 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0 In-Reply-To: <5261BE0C.2000904@pennware.com> Xref: news.gmane.org gmane.linux.lib.musl.general:4134 Archived-At: This is a multi-part message in MIME format. --------------090600000903090203080203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I understand my question is rather stupid, but what is the most preferable way to use ecc as a compiler to build itself? Even if I set cc and cxx variables in the root configure script, it still builds everything with gcc. Is setting CC and CXX environment variables sufficient? Dmitry 19.10.2013 05:02, Richard Pennington ?????: > The clang/LLVM based ELLCC project (http://ellcc.org), after having > reached a huge milestone (http://ellcc.org/blog/?p=231) has now > successfully compiled itself. > > The steps were: > 1. Use gcc to build the compiler with Linux standard libraries. > 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, > and compiler-rt > 3. Use the newly built compiler to build itself again. > > One interesting side note: The compiler was 12MB smaller after it > built itself. > > ct-fw-88 ellcc 622 % size */Release+Asserts/bin/ecc > > text data bss dec hex filename > > 52415858 2152024 84768 54652650 341eeea > llvm-build/Release+Asserts/bin/ecc > > 40222706 2117136 135416 42475258 2881efa > llvm-build-self/Release+Asserts/bin/ecc > > Even more interesting, it was compiled statically. No dynamic > libraries needed: > > ct-fw-88 ellcc 623 % ldd */Release+Asserts/bin/ecc > > llvm-build/Release+Asserts/bin/ecc: > > linux-vdso.so.1 => (0x00007fff2ffff000) > > libz.so.1 => /lib64/libz.so.1 (0x00007facd87e1000) > > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007facd85c4000) > > libncurses.so.5 => /lib64/libncurses.so.5 (0x00007facd837c000) > > librt.so.1 => /lib64/librt.so.1 (0x00007facd8173000) > > libdl.so.2 => /lib64/libdl.so.2 (0x00007facd7f6f000) > > libstdc++.so.6 => /home/de023789/gnulocal/lib64/libstdc++.so.6 > (0x00007facd7c6e000) > > libm.so.6 => /lib64/libm.so.6 (0x00007facd7a18000) > > libgcc_s.so.1 => /home/de023789/gnulocal/lib64/libgcc_s.so.1 > (0x00007facd7803000) > > libc.so.6 => /lib64/libc.so.6 (0x00007facd74a5000) > > /lib64/ld-linux-x86-64.so.2 (0x00007facd89f7000) > > llvm-build-self/Release+Asserts/bin/ecc: > > not a dynamic executable > > ct-fw-88 ellcc 624 % > > That is very cool. > > -Rich > --------------090600000903090203080203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

I understand my question is rather stupid, but what is the most preferable way to use ecc as a compiler to build itself? Even if I set cc and cxx variables in the root configure script, it still builds everything with gcc. Is setting CC and CXX environment variables sufficient?

Dmitry

19.10.2013 05:02, Richard Pennington пишет:

The clang/LLVM based ELLCC project (http://ellcc.org), after having reached a huge milestone (http://ellcc.org/blog/?p=231) has now successfully compiled itself.

The steps were:
1. Use gcc to build the compiler with Linux standard libraries.
2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, and compiler-rt
3. Use the newly built compiler to build itself again.

One interesting side note: The compiler was 12MB smaller after it built itself.

ct-fw-88 ellcc 622 % size */Release+Asserts/bin/ecc

   text    data     bss     dec     hex filename

52415858        2152024   84768 54652650        341eeea llvm-build/Release+Asserts/bin/ecc

40222706        2117136 135416 42475258        2881efa llvm-build-self/Release+Asserts/bin/ecc

Even more interesting, it was compiled statically. No dynamic libraries needed:

ct-fw-88 ellcc 623 % ldd */Release+Asserts/bin/ecc

llvm-build/Release+Asserts/bin/ecc:

        linux-vdso.so.1 => (0x00007fff2ffff000)

        libz.so.1 => /lib64/libz.so.1 (0x00007facd87e1000)

        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007facd85c4000)

        libncurses.so.5 => /lib64/libncurses.so.5 (0x00007facd837c000)

        librt.so.1 => /lib64/librt.so.1 (0x00007facd8173000)

        libdl.so.2 => /lib64/libdl.so.2 (0x00007facd7f6f000)

        libstdc++.so.6 => /home/de023789/gnulocal/lib64/libstdc++.so.6 (0x00007facd7c6e000)

        libm.so.6 => /lib64/libm.so.6 (0x00007facd7a18000)

        libgcc_s.so.1 => /home/de023789/gnulocal/lib64/libgcc_s.so.1 (0x00007facd7803000)

        libc.so.6 => /lib64/libc.so.6 (0x00007facd74a5000)

        /lib64/ld-linux-x86-64.so.2 (0x00007facd89f7000)

llvm-build-self/Release+Asserts/bin/ecc:

        not a dynamic executable

ct-fw-88 ellcc 624 %

That is very cool.

-Rich

--------------090600000903090203080203-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4135 Path: news.gmane.org!not-for-mail From: Rob Landley Newsgroups: gmane.linux.lib.musl.general Subject: Re: ELLCC has self hosted. Date: Sun, 20 Oct 2013 16:05:52 -0500 Message-ID: <1382303152.1974.218@driftwood> References: <526409B7.3090607@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1382303165 27488 80.91.229.3 (20 Oct 2013 21:06:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2013 21:06:05 +0000 (UTC) Cc: musl@lists.openwall.com To: musl@lists.openwall.com Original-X-From: musl-return-4139-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 20 23:06:11 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VY0CQ-0007wk-5q for gllmg-musl@plane.gmane.org; Sun, 20 Oct 2013 23:06:10 +0200 Original-Received: (qmail 3958 invoked by uid 550); 20 Oct 2013 21:06:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 3950 invoked from network); 20 Oct 2013 21:06:08 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:cc:in-reply-to:message-id :mime-version:content-type:content-disposition :content-transfer-encoding; bh=9APihhOzuTqfGWBG3wuWhnwGRMCgCC4YDZfjpqyK7HY=; b=Bn27tExK8myzx4kEb13Srj5fwIsOuJ3+a7BjSi51L2HEwYP+pDAPwi9zfPNjpkxyNv 0pUHxh5ioXgHC/gtrPzO1f0m+3odRzdqPZQsJcrx5lzcNvvr2wJgfW0pML7RM/v8ANJi UbbzlxB56rkRwK0Krl6zQcl/yyOAxU9psMDT94iuZyr0pafRMWlkBiTjbCNC/dwonXIo 7EDV+4ff4mmD4XBf5qg1heU8creOIVDkyHozgYw+qtX/xdZINoCVhIvJg+lpRje/+T+7 QNSGX0vTrYhNmago7NVDNynZGIxQjdkP/N9R4ATs1VgarPIxK037AdynuA//0G1a8YKM cOTg== X-Gm-Message-State: ALoCoQkjgdRybT+YoF1Lsw+Y8eQ8ND2k4wpbWTQv8RR7e2RCvJRq4ZkchUsAiFR3n3MBTRsJaRv2 X-Received: by 10.182.113.195 with SMTP id ja3mr1563289obb.46.1382303155935; Sun, 20 Oct 2013 14:05:55 -0700 (PDT) In-Reply-To: <526409B7.3090607@gmail.com> (from agentprog@gmail.com on Sun Oct 20 11:49:59 2013) X-Mailer: Balsa 2.4.11 Content-Disposition: inline Xref: news.gmane.org gmane.linux.lib.musl.general:4135 Archived-At: I'd cc: the relevant parties but this mailing list is misconfigured =20 with the broken reply-to: tag so I'd have to dig through the backscroll =20 to find out who they are. Oh well. On 10/20/2013 11:49:59 AM, agent wrote: > 19.10.2013 05:02, Richard Pennington ?????: >> The clang/LLVM based ELLCC project (http://ellcc.org), after having =20 >> reached a huge milestone (http://ellcc.org/blog/?p=3D231) has now =20 >> successfully compiled itself. >>=20 >> The steps were: >> 1. Use gcc to build the compiler with Linux standard libraries. >> 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, =20 >> and compiler-rt >> 3. Use the newly built compiler to build itself again. ... >>=20 >> That is very cool. >>=20 >> -Rich >>=20 >=20 > I understand my question is rather stupid, but what is the most =20 > preferable way to > use ecc as a compiler to build itself? Even if I set cc and cxx =20 > variables in the > root configure script, it still builds everything with gcc. Is =20 > setting CC and CXX > environment variables sufficient? >=20 > Dmitry My question is even dumber: why does the ellcc.org download page say =20 the last release was a year ago? Rob = From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4137 Path: news.gmane.org!not-for-mail From: agent Newsgroups: gmane.linux.lib.musl.general Subject: Re: ELLCC has self hosted. Date: Mon, 21 Oct 2013 11:27:58 +0600 Message-ID: <5264BB5E.4070409@gmail.com> References: <1382303152.1974.218@driftwood> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1382333456 10923 80.91.229.3 (21 Oct 2013 05:30:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2013 05:30:56 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4141-gllmg-musl=m.gmane.org@lists.openwall.com Mon Oct 21 07:31:02 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1VY84x-0008VS-6a for gllmg-musl@plane.gmane.org; Mon, 21 Oct 2013 07:30:59 +0200 Original-Received: (qmail 17806 invoked by uid 550); 21 Oct 2013 05:30:57 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 17798 invoked from network); 21 Oct 2013 05:30:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=IQ/LU5tgqBPhbj/iFRyWFkyPMFe/N8ZKglJf8VySYDg=; b=MMtYziJYJNrwGWd7XaDEy3ZpiaQc1S11a67a1EaV7PiJunrj0U/HGO4s2P9EEOk14i /0MFea6f8X6v3641Yvp1zVy1vJWzmUFtefAtgUVQuSKuN3tBdHsxjpVxGcJH+WKWMyTh g3m39XxSo3CzcfUtl3gLSI8zGAON77RXedbFdt3d5edCNrOEOPlVC8KXafubPVhKW2zq kYoGYsMboNSvrIKeq15mdSV7XXCPTl0FT98/3tuZ5BIdLC+SfXY0YJh0o+TPd14X5YWw DypzwC6GQn6r99IS36aVDV6vBIC9tfJtWmucanq4sFP9GA09V1vlA4mA5559czNoEbvf +Rdg== X-Received: by 10.112.89.100 with SMTP id bn4mr12040138lbb.16.1382333446322; Sun, 20 Oct 2013 22:30:46 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0 In-Reply-To: <1382303152.1974.218@driftwood> Xref: news.gmane.org gmane.linux.lib.musl.general:4137 Archived-At: 21.10.2013 03:05, Rob Landley пишет: > I'd cc: the relevant parties but this mailing list is misconfigured > with the broken reply-to: tag so I'd have to dig through the > backscroll to find out who they are. Oh well. > > On 10/20/2013 11:49:59 AM, agent wrote: >> 19.10.2013 05:02, Richard Pennington ?????: >>> The clang/LLVM based ELLCC project (http://ellcc.org), after having >>> reached a huge milestone (http://ellcc.org/blog/?p=231) has now >>> successfully compiled itself. >>> >>> The steps were: >>> 1. Use gcc to build the compiler with Linux standard libraries. >>> 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, >>> and compiler-rt >>> 3. Use the newly built compiler to build itself again. > ... >>> >>> That is very cool. >>> >>> -Rich >>> >> >> I understand my question is rather stupid, but what is the most >> preferable way to >> use ecc as a compiler to build itself? Even if I set cc and cxx >> variables in the >> root configure script, it still builds everything with gcc. Is >> setting CC and CXX >> environment variables sufficient? >> >> Dmitry > > My question is even dumber: why does the ellcc.org download page say > the last release was a year ago? > > Rob > There are only binaries on a download page and I don't believe binary downloads pages any more, so I checked out from SVN repository. I confirm it is able to compile C and C++ code and link it statically with musl libc and clang libc++, but I have this trouble with using it to recompile itself. It compiles about 2 hours on my box so it is quite hard to experiment with environment variables just to find out it was still built with GCC. Dmitry