clang and boost

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

clang and boost

Mark A. Lyan
Dear clang/LLVM gurus-

I'm trying clang (off of the trunk) to try and build our C/C++ sources.

Clang compiled the C files properly and a few C++ files OK as well. The problem I currently see is with C++ sources files that use boost headers. The boost headers have relative paths for some headers and clang is unable to get to them.


Any clues to get this working?

Thanks,
-KC

An example:

clang: warning: argument unused during compilation: '-mcld'
clang: warning: argument unused during compilation: '-fPIE'
In file included from AtomicFileStream.cc:14:
In file included from include/Exceptions.hh:9:
In file included from linux64/include/boost/tr1/tr1/iomanip:16:
bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12: fatal error: '../4.2.1/utility' file not found
#  include BOOST_TR1_STD_HEADER(utility)
           ^
bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44: note: instantiated from:
#        define BOOST_TR1_STD_HEADER(name) <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
                                           ^
1 error generated.


Thanks,
-KC


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

variadic.template
To me, it seems more like a boost-issue than a clang-issue, maybe you are more successful on the boost-mailinglist.

2011/4/6 Mark A. Lyan <[hidden email]>
Dear clang/LLVM gurus-

I'm trying clang (off of the trunk) to try and build our C/C++ sources.

Clang compiled the C files properly and a few C++ files OK as well. The problem I currently see is with C++ sources files that use boost headers. The boost headers have relative paths for some headers and clang is unable to get to them.


Any clues to get this working?

Thanks,
-KC

An example:

clang: warning: argument unused during compilation: '-mcld'
clang: warning: argument unused during compilation: '-fPIE'
In file included from AtomicFileStream.cc:14:
In file included from include/Exceptions.hh:9:
In file included from linux64/include/boost/tr1/tr1/iomanip:16:
bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12: fatal error: '../4.2.1/utility' file not found
#  include BOOST_TR1_STD_HEADER(utility)
           ^
bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44: note: instantiated from:
#        define BOOST_TR1_STD_HEADER(name) <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
                                           ^
1 error generated.


Thanks,
-KC


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev



_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Reid Kleckner-2
IIUC the issue is that clang masquerades as gcc 4.2.1 to match
llvm-gcc, setting __GNUC__, __GNUC_MINOR__, and GNUC_PATCH_LEVEL__ to
4, 2, and 1.  However, Mark doesn't happen to have gcc 4.2.1's
headers.  Boost seems to be attempting to include specifically the
headers that go with the version of the compiler being used.  Clang
will attempt to use the latest gcc headers installed.  Anybody know
why?  IMO this logic should be disabled ifdef __clang__.

Reid

On Thu, Apr 7, 2011 at 6:16 AM, Hendrik vP
<[hidden email]> wrote:

> To me, it seems more like a boost-issue than a clang-issue, maybe you are
> more successful on the boost-mailinglist.
>
> 2011/4/6 Mark A. Lyan <[hidden email]>
>>
>> Dear clang/LLVM gurus-
>>
>> I'm trying clang (off of the trunk) to try and build our C/C++ sources.
>>
>> Clang compiled the C files properly and a few C++ files OK as well. The
>> problem I currently see is with C++ sources files that use boost headers.
>> The boost headers have relative paths for some headers and clang is unable
>> to get to them.
>>
>>
>> Any clues to get this working?
>>
>> Thanks,
>> -KC
>>
>> An example:
>>
>> clang: warning: argument unused during compilation: '-mcld'
>> clang: warning: argument unused during compilation: '-fPIE'
>> In file included from AtomicFileStream.cc:14:
>> In file included from include/Exceptions.hh:9:
>> In file included from linux64/include/boost/tr1/tr1/iomanip:16:
>>
>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12:
>> fatal error: '../4.2.1/utility' file not found
>> #  include BOOST_TR1_STD_HEADER(utility)
>>            ^
>>
>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44:
>> note: instantiated from:
>> #        define BOOST_TR1_STD_HEADER(name)
>> <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
>>                                            ^
>> 1 error generated.
>>
>>
>> Thanks,
>> -KC
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>
>
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Christopher Jefferson

On 7 Apr 2011, at 17:17, Reid Kleckner wrote:

> IIUC the issue is that clang masquerades as gcc 4.2.1 to match
> llvm-gcc, setting __GNUC__, __GNUC_MINOR__, and GNUC_PATCH_LEVEL__ to
> 4, 2, and 1.  However, Mark doesn't happen to have gcc 4.2.1's
> headers.  Boost seems to be attempting to include specifically the
> headers that go with the version of the compiler being used.  Clang
> will attempt to use the latest gcc headers installed.  Anybody know
> why?  IMO this logic should be disabled ifdef __clang__.
>

Which boost version are you using?

Only very recently has boost and clang started working well together. I would advise upgrading to the latest version of boost.

Chris

> Reid
>
> On Thu, Apr 7, 2011 at 6:16 AM, Hendrik vP
> <[hidden email]> wrote:
>> To me, it seems more like a boost-issue than a clang-issue, maybe you are
>> more successful on the boost-mailinglist.
>>
>> 2011/4/6 Mark A. Lyan <[hidden email]>
>>>
>>> Dear clang/LLVM gurus-
>>>
>>> I'm trying clang (off of the trunk) to try and build our C/C++ sources.
>>>
>>> Clang compiled the C files properly and a few C++ files OK as well. The
>>> problem I currently see is with C++ sources files that use boost headers.
>>> The boost headers have relative paths for some headers and clang is unable
>>> to get to them.
>>>
>>>
>>> Any clues to get this working?
>>>
>>> Thanks,
>>> -KC
>>>
>>> An example:
>>>
>>> clang: warning: argument unused during compilation: '-mcld'
>>> clang: warning: argument unused during compilation: '-fPIE'
>>> In file included from AtomicFileStream.cc:14:
>>> In file included from include/Exceptions.hh:9:
>>> In file included from linux64/include/boost/tr1/tr1/iomanip:16:
>>>
>>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12:
>>> fatal error: '../4.2.1/utility' file not found
>>> #  include BOOST_TR1_STD_HEADER(utility)
>>>            ^
>>>
>>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44:
>>> note: instantiated from:
>>> #        define BOOST_TR1_STD_HEADER(name)
>>> <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
>>>                                            ^
>>> 1 error generated.
>>>
>>>
>>> Thanks,
>>> -KC
>>>
>>>
>>> _______________________________________________
>>> cfe-dev mailing list
>>> [hidden email]
>>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>>
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Mark A. Lyan
Thanks Christopher.

On Thu, Apr 7, 2011 at 10:22 AM, Christopher Jefferson <[hidden email]> wrote:

On 7 Apr 2011, at 17:17, Reid Kleckner wrote:

> IIUC the issue is that clang masquerades as gcc 4.2.1 to match
> llvm-gcc, setting __GNUC__, __GNUC_MINOR__, and GNUC_PATCH_LEVEL__ to
> 4, 2, and 1.  However, Mark doesn't happen to have gcc 4.2.1's
> headers.  Boost seems to be attempting to include specifically the
> headers that go with the version of the compiler being used.  Clang
> will attempt to use the latest gcc headers installed.  Anybody know
> why?  IMO this logic should be disabled ifdef __clang__.
>
 
Which boost version are you using?


I'm using boost-1.43 as of now. But, will try to upgrade to 1.46.1 and see if that helps.

Only very recently has boost and clang started working well together. I would advise upgrading to the latest version of boost.

Chris

> Reid
>
> On Thu, Apr 7, 2011 at 6:16 AM, Hendrik vP
> <[hidden email]> wrote:
>> To me, it seems more like a boost-issue than a clang-issue, maybe you are
>> more successful on the boost-mailinglist.
>>
>> 2011/4/6 Mark A. Lyan <[hidden email]>
>>>
>>> Dear clang/LLVM gurus-
>>>
>>> I'm trying clang (off of the trunk) to try and build our C/C++ sources.
>>>
>>> Clang compiled the C files properly and a few C++ files OK as well. The
>>> problem I currently see is with C++ sources files that use boost headers.
>>> The boost headers have relative paths for some headers and clang is unable
>>> to get to them.
>>>
>>>
>>> Any clues to get this working?
>>>
>>> Thanks,
>>> -KC
>>>
>>> An example:
>>>
>>> clang: warning: argument unused during compilation: '-mcld'
>>> clang: warning: argument unused during compilation: '-fPIE'
>>> In file included from AtomicFileStream.cc:14:
>>> In file included from include/Exceptions.hh:9:
>>> In file included from linux64/include/boost/tr1/tr1/iomanip:16:
>>>
>>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12:
>>> fatal error: '../4.2.1/utility' file not found
>>> #  include BOOST_TR1_STD_HEADER(utility)
>>>            ^
>>>
>>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44:
>>> note: instantiated from:
>>> #        define BOOST_TR1_STD_HEADER(name)
>>> <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
>>>                                            ^
>>> 1 error generated.
>>>
>>>
>>> Thanks,
>>> -KC
>>>
>>>
>>> _______________________________________________
>>> cfe-dev mailing list
>>> [hidden email]
>>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>>
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev



_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Mark A. Lyan
In reply to this post by Reid Kleckner-2


On Thu, Apr 7, 2011 at 9:17 AM, Reid Kleckner <[hidden email]> wrote:
IIUC the issue is that clang masquerades as gcc 4.2.1 to match
llvm-gcc, setting __GNUC__, __GNUC_MINOR__, and GNUC_PATCH_LEVEL__ to
4, 2, and 1.  However, Mark doesn't happen to have gcc 4.2.1's
headers.  Boost seems to be attempting to include specifically the
headers that go with the version of the compiler being used.  Clang
will attempt to use the latest gcc headers installed.  Anybody know
why?  IMO this logic should be disabled ifdef __clang__.

Hm.. interesting. So, if I were to add a __clang__ clause and define my own path there, it would work, but, I do not want to patching boost and carry these patches on, everytime I upgrade.

But, that might work for the near future. Thanks much for your advice.
 

Reid

On Thu, Apr 7, 2011 at 6:16 AM, Hendrik vP
<[hidden email]> wrote:
> To me, it seems more like a boost-issue than a clang-issue, maybe you are
> more successful on the boost-mailinglist.
>
> 2011/4/6 Mark A. Lyan <[hidden email]>
>>
>> Dear clang/LLVM gurus-
>>
>> I'm trying clang (off of the trunk) to try and build our C/C++ sources.
>>
>> Clang compiled the C files properly and a few C++ files OK as well. The
>> problem I currently see is with C++ sources files that use boost headers.
>> The boost headers have relative paths for some headers and clang is unable
>> to get to them.
>>
>>
>> Any clues to get this working?
>>
>> Thanks,
>> -KC
>>
>> An example:
>>
>> clang: warning: argument unused during compilation: '-mcld'
>> clang: warning: argument unused during compilation: '-fPIE'
>> In file included from AtomicFileStream.cc:14:
>> In file included from include/Exceptions.hh:9:
>> In file included from linux64/include/boost/tr1/tr1/iomanip:16:
>>
>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:151:12:
>> fatal error: '../4.2.1/utility' file not found
>> #  include BOOST_TR1_STD_HEADER(utility)
>>            ^
>>
>> bora/build/package/COMPONENTS/boost1430_lin64_gcc412/ob-387294/linux64/include/boost/tr1/detail/config_all.hpp:95:44:
>> note: instantiated from:
>> #        define BOOST_TR1_STD_HEADER(name)
>> <../__GNUC__.__GNUC_MINOR__.__GNUC_PATCHLEVEL__/name>
>>                                            ^
>> 1 error generated.
>>
>>
>> Thanks,
>> -KC
>>
>>
>> _______________________________________________
>> cfe-dev mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>
>
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Jonathan Sauer
Hello,

> Hm.. interesting. So, if I were to add a __clang__ clause and define my own path there, it would work, but, I do not want to patching boost and carry these patches on, everytime I upgrade.

Using boost 1.46.1 here. I just compiled the following line successfully with clang 128404:

#include <boost/tr1/tr1/iomanip>

I only got two warnings about #include_next being an extension.

Boost got support for clang in 1.46.1 (including recognizing its C++0x features).


Jonathan


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
lis
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

lis
I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0. One problem I have is that $(Includes) is not set when build with bjam. I tried to workaround that by modifying clang-linux.jam to hard-code the include path.

actions compile.c++.without-pth {
  "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES) -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers" -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost" -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
}

 This helped to get around some of the include path issues but I stuck with the following message:

In file included from C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12: fatal error
: '../include/utility' file not found
#  include BOOST_TR1_STD_HEADER(utility)
           ^
C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41: note: instantiated from:
#     define BOOST_TR1_STD_HEADER(name) <../include/name>

My question is: What do I need to do to get Clang to set up the include path correctly?
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Richard Smith
On Tue, Nov 13, 2012 at 5:42 PM, lis <[hidden email]> wrote:

> I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0. One
> problem I have is that $(Includes) is not set when build with bjam. I tried
> to workaround that by modifying clang-linux.jam to hard-code the include
> path.
>
> actions compile.c++.without-pth {
>   "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES)
> -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers"
> -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost"
> -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
> }
>
>  This helped to get around some of the include path issues but I stuck with
> the following message:
>
> In file included from C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12: fatal
> error
> : '../include/utility' file not found
> #  include BOOST_TR1_STD_HEADER(utility)
>            ^
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41: note:
> instantiated from:
> #     define BOOST_TR1_STD_HEADER(name) <../include/name>
>
> My question is: What do I need to do to get Clang to set up the include path
> correctly?

I'm not sure what the problem is, but you should use a newer version
of Clang. Clang development moves fast, and version 2.9 is now very
far behind in terms of language support.
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
lis
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

lis
Richard Smith wrote
On Tue, Nov 13, 2012 at 5:42 PM, lis <[hidden email]> wrote:
> I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0. One
> problem I have is that $(Includes) is not set when build with bjam. I tried
> to workaround that by modifying clang-linux.jam to hard-code the include
> path.
>
> actions compile.c++.without-pth {
>   "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES)
> -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers"
> -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost"
> -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
> }
>
>  This helped to get around some of the include path issues but I stuck with
> the following message:
>
> In file included from C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12: fatal
> error
> : '../include/utility' file not found
> #  include BOOST_TR1_STD_HEADER(utility)
>            ^
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41: note:
> instantiated from:
> #     define BOOST_TR1_STD_HEADER(name) <../include/name>
>
> My question is: What do I need to do to get Clang to set up the include path
> correctly?

I'm not sure what the problem is, but you should use a newer version
of Clang. Clang development moves fast, and version 2.9 is now very
far behind in terms of language support.
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

I downloaded the latest 3.1 clang from MingW from http://llvm.org/releases/download.html  and it looks like it is using Visual Studio include headers as the default. How can I reset it to use boost headers or GCC headers?
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

Nikola Smiljanic
Pass it -triple i386-pc-mingw32, but this will probably assume that your mingw is located in C:\mingw


On Thu, Nov 15, 2012 at 7:10 AM, lis <[hidden email]> wrote:
Richard Smith wrote
> On Tue, Nov 13, 2012 at 5:42 PM, lis <

> li_shao1@

> > wrote:
>> I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0.
>> One
>> problem I have is that $(Includes) is not set when build with bjam. I
>> tried
>> to workaround that by modifying clang-linux.jam to hard-code the include
>> path.
>>
>> actions compile.c++.without-pth {
>>   "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES)
>> -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers"
>> -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost"
>> -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
>> }
>>
>>  This helped to get around some of the include path issues but I stuck
>> with
>> the following message:
>>
>> In file included from
>> C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
>> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12:
>> fatal
>> error
>> : '../include/utility' file not found
>> #  include BOOST_TR1_STD_HEADER(utility)
>>            ^
>> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41: note:
>> instantiated from:
>> #     define BOOST_TR1_STD_HEADER(name) <../include/name>
>>
>> My question is: What do I need to do to get Clang to set up the include
>> path
>> correctly?
>
> I'm not sure what the problem is, but you should use a newer version
> of Clang. Clang development moves fast, and version 2.9 is now very
> far behind in terms of language support.
> _______________________________________________
> cfe-dev mailing list

> cfe-dev@.uiuc

> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev


I downloaded the latest 3.1 clang from MingW from
http://llvm.org/releases/download.html  and it looks like it is using Visual
Studio include headers as the default. How can I reset it to use boost
headers or GCC headers?



--
View this message in context: http://clang-developers.42468.n3.nabble.com/clang-and-boost-tp2788340p4028236.html
Sent from the Clang Developers mailing list archive at Nabble.com.
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
lis
Reply | Threaded
Open this post in threaded view
|

Re: clang and boost

lis
I made change in the .jam file with the following:

actions compile.c++.without-pth {
  "$(CONFIG_COMMAND)" -triple i386-pc-mingw32 -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES) -I"$(INCLUDES)" -o "$(<)" "$(>)"
}

I am still getting the same error of using Visual Studio include headers. I have MingW toolset installed on C:\mingW

Nikola Smiljanic wrote
Pass it -triple i386-pc-*mingw32, but this will probably assume that your
mingw is located in C:\mingw*


On Thu, Nov 15, 2012 at 7:10 AM, lis <[hidden email]> wrote:

> Richard Smith wrote
> > On Tue, Nov 13, 2012 at 5:42 PM, lis <
>
> > li_shao1@
>
> > > wrote:
> >> I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0.
> >> One
> >> problem I have is that $(Includes) is not set when build with bjam. I
> >> tried
> >> to workaround that by modifying clang-linux.jam to hard-code the include
> >> path.
> >>
> >> actions compile.c++.without-pth {
> >>   "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES)
> >> -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers"
> >> -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost"
> >> -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
> >> }
> >>
> >>  This helped to get around some of the include path issues but I stuck
> >> with
> >> the following message:
> >>
> >> In file included from
> >> C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
> >> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12:
> >> fatal
> >> error
> >> : '../include/utility' file not found
> >> #  include BOOST_TR1_STD_HEADER(utility)
> >>            ^
> >> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41:
> note:
> >> instantiated from:
> >> #     define BOOST_TR1_STD_HEADER(name) <../include/name>
> >>
> >> My question is: What do I need to do to get Clang to set up the include
> >> path
> >> correctly?
> >
> > I'm not sure what the problem is, but you should use a newer version
> > of Clang. Clang development moves fast, and version 2.9 is now very
> > far behind in terms of language support.
> > _______________________________________________
> > cfe-dev mailing list
>
> > cfe-dev@.uiuc
>
> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
> I downloaded the latest 3.1 clang from MingW from
> http://llvm.org/releases/download.html  and it looks like it is using
> Visual
> Studio include headers as the default. How can I reset it to use boost
> headers or GCC headers?
>
>
>
> --
> View this message in context:
> http://clang-developers.42468.n3.nabble.com/clang-and-boost-tp2788340p4028236.html
> Sent from the Clang Developers mailing list archive at Nabble.com.
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev