Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs:
#include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }
Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^ 1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
-Tyler
On Mon, Mar 24, 2014 at 6:38 PM, Tyler Brock tyler.brock@gmail.com wrote:
Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs: #include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
To my knowledge it was originally based on CentOS but it has since diverged.
It may be useful to mention that this same issue affects multiple Red Hat derivatives (including RHEL 6.4 itself) and not just Amazon Linux. I attempted the same process on Red Hat 6.4, Fedora 20, and Amazon Linux 2013.09, and it fails on all three of these distributions with the same errors. In fact, the only distribution on which I have been able to get it to work is CentOS 6.4.
-Tyler
On Tue, Mar 25, 2014 at 1:46 AM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Mar 24, 2014 at 6:38 PM, Tyler Brock tyler.brock@gmail.comwrote:
Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs: #include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Here is a gist containing the output of attempting to compile the program after installing the clang package on each platform I mentioned:
https://gist.github.com/TylerBrock/9771402
-Tyler
On Tue, Mar 25, 2014 at 4:54 PM, Tyler Brock tyler.brock@gmail.com wrote:
To my knowledge it was originally based on CentOS but it has since diverged.
It may be useful to mention that this same issue affects multiple Red Hat derivatives (including RHEL 6.4 itself) and not just Amazon Linux. I attempted the same process on Red Hat 6.4, Fedora 20, and Amazon Linux 2013.09, and it fails on all three of these distributions with the same errors. In fact, the only distribution on which I have been able to get it to work is CentOS 6.4.
-Tyler
On Tue, Mar 25, 2014 at 1:46 AM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Mar 24, 2014 at 6:38 PM, Tyler Brock tyler.brock@gmail.comwrote:
Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs: #include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Tue, Mar 25, 2014 at 2:08 PM, Tyler Brock tyler.brock@gmail.com wrote:
Here is a gist containing the output of attempting to compile the program after installing the clang package on each platform I mentioned:
https://gist.github.com/TylerBrock/9771402
-Tyler
On Tue, Mar 25, 2014 at 4:54 PM, Tyler Brock tyler.brock@gmail.comwrote:
To my knowledge it was originally based on CentOS but it has since diverged.
It may be useful to mention that this same issue affects multiple Red Hat derivatives (including RHEL 6.4 itself) and not just Amazon Linux. I attempted the same process on Red Hat 6.4, Fedora 20, and Amazon Linux 2013.09, and it fails on all three of these distributions with the same errors. In fact, the only distribution on which I have been able to get it to work is CentOS 6.4.
-Tyler
On Tue, Mar 25, 2014 at 1:46 AM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Mar 24, 2014 at 6:38 PM, Tyler Brock tyler.brock@gmail.comwrote:
Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs: #include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
I've tested on CentOS 6.5, RHEL 6.5 and RHEL 6.4 and all of them work. Do you have the package libstdc++-devel installed? That package not being installed is the only thing that I can think of that might be causing this problem and maybe that package should be listed as a requires in the .spec for clang.
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
Any other thoughts?
-Tyler
On Wed, Mar 26, 2014 at 12:07 AM, Dave Johansen davejohansen@gmail.comwrote:
On Tue, Mar 25, 2014 at 2:08 PM, Tyler Brock tyler.brock@gmail.comwrote:
Here is a gist containing the output of attempting to compile the program after installing the clang package on each platform I mentioned:
https://gist.github.com/TylerBrock/9771402
-Tyler
On Tue, Mar 25, 2014 at 4:54 PM, Tyler Brock tyler.brock@gmail.comwrote:
To my knowledge it was originally based on CentOS but it has since diverged.
It may be useful to mention that this same issue affects multiple Red Hat derivatives (including RHEL 6.4 itself) and not just Amazon Linux. I attempted the same process on Red Hat 6.4, Fedora 20, and Amazon Linux 2013.09, and it fails on all three of these distributions with the same errors. In fact, the only distribution on which I have been able to get it to work is CentOS 6.4.
-Tyler
On Tue, Mar 25, 2014 at 1:46 AM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Mar 24, 2014 at 6:38 PM, Tyler Brock tyler.brock@gmail.comwrote:
Hey Everyone,
I've been trying to use clang package on Amazon linux via EPEL and have installed version 3.4-9.el6 yet am unable to compile even the simplest of programs: #include <iostream>
int main(){ std::cout << "Hello World" << std::endl; }Saving the above into a file named test.cpp and compiling with "clang++ test.cpp" produces the following error:
test.cpp:1:10: fatal error: 'iostream' file not found #include <iostream> ^1 error generated.
When attempting the same with gcc (g++) it works as expected so It seems like the clang compiler cannot find the required C++ headers and library files.
I have contacted Amazon AWS support and they verified that the issue is reproducible by them running the latest version of Amazon Linux with updated packages from EPEL.
I've tried installing devel headers for clang and multiple versions of libstd++ which seem to be placed in /usr/include/c++/<gcc-version> but which, when used by gcc, do not require the path to them be specified at all. It just works.
I have a feeling the clang package is not built to work properly with Amazon Linux as C++ headers and library files (for either for libc++ or libstdc++) such as iostream should be found by default. Any help in resolving the matter would be greatly appreciated.
It may also be worth noting that on CentOS the clang package seems to work fine.
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
I've tested on CentOS 6.5, RHEL 6.5 and RHEL 6.4 and all of them work. Do you have the package libstdc++-devel installed? That package not being installed is the only thing that I can think of that might be causing this problem and maybe that package should be listed as a requires in the .spec for clang.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Tue, Apr 1, 2014 at 1:11 PM, Tyler Brock tyler.brock@gmail.com wrote:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
Any other thoughts?
libstdc++-devel is the one you need to check, because that's the one with the headers and such.
2014-04-01 22:23 GMT+02:00 Dave Johansen davejohansen@gmail.com:
On Tue, Apr 1, 2014 at 1:11 PM, Tyler Brock tyler.brock@gmail.com wrote:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
Any other thoughts?
libstdc++-devel is the one you need to check, because that's the one with the headers and such.
I know nothing about C++ nor clang, but isn't the include supposed to include <iostream.h> or <iostream.hpp>?
<iostream> without a file extension could seem a bit short to me.
Regards,
J.
2014-04-01 22:27 GMT+02:00 Jérôme Fenal jfenal@gmail.com:
2014-04-01 22:23 GMT+02:00 Dave Johansen davejohansen@gmail.com:
On Tue, Apr 1, 2014 at 1:11 PM, Tyler Brock tyler.brock@gmail.com wrote:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
Any other thoughts?
libstdc++-devel is the one you need to check, because that's the one with the headers and such.
I know nothing about C++ nor clang, but isn't the include supposed to include <iostream.h> or <iostream.hpp>?
<iostream> without a file extension could seem a bit short to me.
Scratch that... did my homework in the mean time :-)
1.4.2014 23.11, Tyler Brock kirjoitti:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
It might be worth mentioning that the Amazon-provided libstdc++-devel is 4.6.3-3.10.amzn1, and it doesn't seem to provide /usr/include/c++/4.4.4/iostream like the CentOS version does.
On Tue, Apr 1, 2014 at 1:25 PM, Anssi Johansson epel@miuku.net wrote:
1.4.2014 23.11, Tyler Brock kirjoitti:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
It might be worth mentioning that the Amazon-provided libstdc++-devel is 4.6.3-3.10.amzn1, and it doesn't seem to provide /usr/include/c++/4.4.4/iostream like the CentOS version does.
What does running "yum provides /usr/include/c++/4.4.4/iostream" on one of these Amazon boxes output?
Ok, the problem is that clang doesn't know about the amazon-linux triples. We need to apply this patch so that it will work:
http://marc.info/?l=cfe-commits&m=135178300407811&q=p3
The patch will not effect clang in any way except for adding the ability to support amazon linux. What do we need to do in order for this patch to be applied to the EPEL provided package during build?
-Tyler
On Tue, Apr 1, 2014 at 4:33 PM, Dave Johansen davejohansen@gmail.comwrote:
On Tue, Apr 1, 2014 at 1:25 PM, Anssi Johansson epel@miuku.net wrote:
1.4.2014 23.11, Tyler Brock kirjoitti:
Thanks so much for looking into this Dave. Yes, libstdc++ was installed.
It might be worth mentioning that the Amazon-provided libstdc++-devel is 4.6.3-3.10.amzn1, and it doesn't seem to provide /usr/include/c++/4.4.4/iostream like the CentOS version does.
What does running "yum provides /usr/include/c++/4.4.4/iostream" on one of these Amazon boxes output?
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, Apr 16, 2014 at 11:01 AM, Tyler Brock tyler.brock@gmail.com wrote:
Ok, the problem is that clang doesn't know about the amazon-linux triples. We need to apply this patch so that it will work:
http://marc.info/?l=cfe-commits&m=135178300407811&q=p3
The patch will not effect clang in any way except for adding the ability to support amazon linux. What do we need to do in order for this patch to be applied to the EPEL provided package during build?
The patch took a little modification to apply against the release of 3.4, but I'm building with it now on my machine. If I make the .rpms available somewhere, then could you test them to make sure that this resolves the issue. I'd prefer to test this fix before committing it into the EPEL repos and starting the testing period.
Thanks, Dave
Of course, I would be happy to help. Yes, the patch I found was old. I also had to make some changes and can confirm similar modifications worked against clang 3.4.
I would be happy to test whatever you send me. Thanks!
On Apr 16, 2014, at 11:40 PM, Dave Johansen davejohansen@gmail.com wrote:
On Wed, Apr 16, 2014 at 11:01 AM, Tyler Brock tyler.brock@gmail.com wrote: Ok, the problem is that clang doesn't know about the amazon-linux triples. We need to apply this patch so that it will work:
http://marc.info/?l=cfe-commits&m=135178300407811&q=p3
The patch will not effect clang in any way except for adding the ability to support amazon linux. What do we need to do in order for this patch to be applied to the EPEL provided package during build?
The patch took a little modification to apply against the release of 3.4, but I'm building with it now on my machine. If I make the .rpms available somewhere, then could you test them to make sure that this resolves the issue. I'd prefer to test this fix before committing it into the EPEL repos and starting the testing period.
Thanks, Dave _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Hey Dave, hope you had a nice weekend.
Any update on the rpms?
-Tyler
On Thu, Apr 17, 2014 at 8:00 AM, Tyler Brock tyler.brock@gmail.com wrote:
Of course, I would be happy to help. Yes, the patch I found was old. I also had to make some changes and can confirm similar modifications worked against clang 3.4.
I would be happy to test whatever you send me. Thanks!
On Apr 16, 2014, at 11:40 PM, Dave Johansen davejohansen@gmail.com wrote:
On Wed, Apr 16, 2014 at 11:01 AM, Tyler Brock tyler.brock@gmail.comwrote:
Ok, the problem is that clang doesn't know about the amazon-linux triples. We need to apply this patch so that it will work:
http://marc.info/?l=cfe-commits&m=135178300407811&q=p3
The patch will not effect clang in any way except for adding the ability to support amazon linux. What do we need to do in order for this patch to be applied to the EPEL provided package during build?
The patch took a little modification to apply against the release of 3.4, but I'm building with it now on my machine. If I make the .rpms available somewhere, then could you test them to make sure that this resolves the issue. I'd prefer to test this fix before committing it into the EPEL repos and starting the testing period.
Thanks, Dave
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Mon, Apr 21, 2014 at 11:40 AM, Tyler Brock tyler.brock@gmail.com wrote:
Hey Dave, hope you had a nice weekend.
Any update on the rpms?
Repos for x86 32-bit and 64-bit can be found at: http://daveisfera.fedorapeople.org/yum/llvm-3.4/
Tested it on the latest amazon linux and it works perfectly. Thank you!
What are the next steps to get the change into EPEL?
-Tyler
On Tue, Apr 22, 2014 at 10:07 PM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Apr 21, 2014 at 11:40 AM, Tyler Brock tyler.brock@gmail.comwrote:
Hey Dave, hope you had a nice weekend.
Any update on the rpms?
Repos for x86 32-bit and 64-bit can be found at: http://daveisfera.fedorapeople.org/yum/llvm-3.4/
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, Apr 23, 2014 at 7:28 AM, Tyler Brock tyler.brock@gmail.com wrote:
Tested it on the latest amazon linux and it works perfectly. Thank you!
What are the next steps to get the change into EPEL?
-Tyler
I'll add the patch to the git branch of llvm for EPEL6 and do the build. It will then be available in the testing repos and I can then transfer it to the release repos 14 days later.
The patch should also be submitted upstream to fix the issue globally and maybe it could even be considered as part of the upcoming 3.4.1 release.
Dave
Great, will you let me know when it goes into testing?
-Tyler
On Wed, Apr 23, 2014 at 11:56 AM, Dave Johansen davejohansen@gmail.comwrote:
On Wed, Apr 23, 2014 at 7:28 AM, Tyler Brock tyler.brock@gmail.comwrote:
Tested it on the latest amazon linux and it works perfectly. Thank you!
What are the next steps to get the change into EPEL?
-Tyler
I'll add the patch to the git branch of llvm for EPEL6 and do the build. It will then be available in the testing repos and I can then transfer it to the release repos 14 days later.
The patch should also be submitted upstream to fix the issue globally and maybe it could even be considered as part of the upcoming 3.4.1 release.
Dave
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, Apr 23, 2014 at 9:06 AM, Tyler Brock tyler.brock@gmail.com wrote:
Great, will you let me know when it goes into testing?
-Tyler
I submitted the .rpm with the patch applied for testing it should be available in the testing repo relatively soon: https://admin.fedoraproject.org/updates/llvm-3.4-10.el6
On Thu, Apr 24, 2014 at 1:30 PM, Dave Johansen davejohansen@gmail.comwrote:
On Wed, Apr 23, 2014 at 9:06 AM, Tyler Brock tyler.brock@gmail.comwrote:
Great, will you let me know when it goes into testing?
-Tyler
I submitted the .rpm with the patch applied for testing it should be available in the testing repo relatively soon: https://admin.fedoraproject.org/updates/llvm-3.4-10.el6
I also opened a bug against clang to see if this change could be made part of the official release ( http://llvm.org/bugs/show_bug.cgi?id=19550 ).
Boss mode. Thanks Dave.
On Apr 24, 2014, at 4:53 PM, Dave Johansen davejohansen@gmail.com wrote:
On Thu, Apr 24, 2014 at 1:30 PM, Dave Johansen davejohansen@gmail.com wrote:
On Wed, Apr 23, 2014 at 9:06 AM, Tyler Brock tyler.brock@gmail.com wrote: Great, will you let me know when it goes into testing?
-Tyler
I submitted the .rpm with the patch applied for testing it should be available in the testing repo relatively soon: https://admin.fedoraproject.org/updates/llvm-3.4-10.el6
I also opened a bug against clang to see if this change could be made part of the official release ( http://llvm.org/bugs/show_bug.cgi?id=19550 ). _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Update: testing packages work as advertised. Just wanted to keep you updated and thank you again.
Will this go into the standard EPEL automatically or do we need to do something else at this point?
-Tyler
On Thu, Apr 24, 2014 at 5:11 PM, Tyler Brock tyler.brock@gmail.com wrote:
Boss mode. Thanks Dave.
On Apr 24, 2014, at 4:53 PM, Dave Johansen davejohansen@gmail.com wrote:
On Thu, Apr 24, 2014 at 1:30 PM, Dave Johansen davejohansen@gmail.comwrote:
On Wed, Apr 23, 2014 at 9:06 AM, Tyler Brock tyler.brock@gmail.comwrote:
Great, will you let me know when it goes into testing?
-Tyler
I submitted the .rpm with the patch applied for testing it should be available in the testing repo relatively soon: https://admin.fedoraproject.org/updates/llvm-3.4-10.el6
I also opened a bug against clang to see if this change could be made part of the official release ( http://llvm.org/bugs/show_bug.cgi?id=19550 ).
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Mon, Apr 28, 2014 at 12:46 PM, Tyler Brock tyler.brock@gmail.com wrote:
Update: testing packages work as advertised. Just wanted to keep you updated and thank you again.
Will this go into the standard EPEL automatically or do we need to do something else at this point?
Bodhi (the Fedora/EPEL update publication system) uses karma and delay times for testing of updates. You can read the details here ( http://fedoraproject.org/wiki/How_to_test_updates ), but basically, if the package gets enough karma it can be pushed out sooner but otherwise it can be rolled out to the official repos 14 days after being available in the testing repos. So once that time has passed, I'll put in the request that it be moved to the official repos.
On Mon, Apr 28, 2014 at 1:11 PM, Dave Johansen davejohansen@gmail.comwrote:
On Mon, Apr 28, 2014 at 12:46 PM, Tyler Brock tyler.brock@gmail.comwrote:
Update: testing packages work as advertised. Just wanted to keep you updated and thank you again.
Will this go into the standard EPEL automatically or do we need to do something else at this point?
Bodhi (the Fedora/EPEL update publication system) uses karma and delay times for testing of updates. You can read the details here ( http://fedoraproject.org/wiki/How_to_test_updates ), but basically, if the package gets enough karma it can be pushed out sooner but otherwise it can be rolled out to the official repos 14 days after being available in the testing repos. So once that time has passed, I'll put in the request that it be moved to the official repos.
This update has been moved to the stable repo.
<snip>
I'm the maintainer of clang in the EPEL, but honestly I know nothing about Amazon Linux. Is it an "EL variant" or claim any sort of compatibility with EL? A known issue even on EL/CentOS with clang is that much of the C++11/14 support won't work because of the old version of the standard library that is available on EL. It sounds like this isn't your issue, but if C++11/14 support is desired, then the devtoolset ( http://rhn.redhat.com/errata/RHEA-2013-1226.html ) is the best route to follow.
We've had the same issues being compatible with Amazon linux at Puppet Labs. Amazon linux is very interesting, in that it's pretty odd.
Depending on which AMI you're on, the compatibility with RHEL is pretty varied. The newest AMI (from April of this year) is closer to RHEL7 or Fedora 20 than EL6, so many items attempting to use EPEL 6 would fail. The last AMI from Oct (I think) is a weird hybrid of EL6 and Fedora 18. It's just difficult to plan for. I don't know how most people use Amazon Linux if they ever need any packages outside of its own package set.
So, I don't have a lot of helpful information, but I thought I'd chime in with my findings from bug triage on Amazon Linux.
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
epel-devel@lists.fedoraproject.org
-
Anssi Johansson -
Dave Johansen -
Jérôme Fenal -
Michael Stahnke -
Tyler Brock