Bug 174589 - devel/icu: clang build of icu-50.1 broken
Summary: devel/icu: clang build of icu-50.1 broken
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: FreeBSD Office Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-20 15:10 UTC by Bernard Spil
Modified: 2013-10-18 16:45 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Spil freebsd_committer 2012-12-20 15:10:00 UTC
Building icu with clang failed with 

} ERRORS (123) in UTextTest( 1.06s )
} ERRORS (97) in UCharsTrieTest (325ms)

--------------------------------------
Errors in total: 220.
            TextTest
         UTextTest
            TestBranches
            TestLongSequence
            TestLongBranch
            TestValuesForState
            TestNextForCodePoint
         UCharsTrieTest
      utility

--------------------------------------
Elapsed Time: 00:04:38.261
*** Error code 220

Stop in /usr/ports/devel/icu.

Building with gcc (base) is succesful.

Looks like there's a problem with the configure script, it detects gcc but it's actually clang.

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-cpp

How-To-Repeat: Build devel/icu with clang
FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
Target: i386-unknown-freebsd9.0
Thread model: posix
Comment 1 Edwin Groothuis freebsd_committer 2012-12-20 15:10:08 UTC
Responsible Changed
From-To: freebsd-ports-bugs->office

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Tijl Coosemans freebsd_committer 2013-10-18 16:44:00 UTC
State Changed
From-To: open->closed

This seems to have been fixed with newer versions of the port and/or 
clang.  Let me know if this is not the case.