On Wed, 29 May 2013 11:39:55 -0400, Mike Jakubik
<mike.jaku...@intertainservices.com> wrote: 
>
>On 05/29/13 03:56, Waitman Gobble wrote:
>> On Mon, 27 May 2013 13:10:52 -0400, Mike Jakubik
>> <mike.jaku...@intertainservices.com> wrote:
>>> Hello,
>>>
>>> I am unable to compile this port, below is the output from gcc48 and
>>> clang 3.2.
>>>
>>> 9.1-STABLE FreeBSD 9.1-STABLE #0: Wed May 15 17:07:33 EDT 2013
>>>
>>> gmake[4]: Entering directory
>>> ../../lib/.libs/libvisio-0.0.so: undefined reference to
>>> `std::ctype<char>::_M_widen_init() const'
>>> collect2: error: ld returned 1 exit status
>>> gmake[4]: *** [vsd2raw] Error 1
>>>
>>>
>>>
>> Hi,
>>
>> Check that /etc/libmap.conf is empty or non-existent,
>> deinstall,rebuild and reinstall graphics/libwpg then build
textproc/libvisio
>> It seems to work with clang (ports version) on FreeBSD 10.0-CURRENT
>>
>>
>
>Hello,
>
>I am using clang for base and gcc48 for ports, i have populated 
>/etc/libmap.conf per the freebsd handbook with the following:
>
>libgcc_s.so.1   gcc48/libgcc_s.so.1
>libgomp.so.1    gcc48/libgomp.so.1
>libobjc.so.3    gcc48/libobjc.so.2
>libssp.so.0     gcc48/libssp.so.0
>libstdc++.so.6  gcc48/libstdc++.so.6
>
>Is this not the right way for clang and gcc to co-exist?
>
>Thank you.
>
>_______________________________________________
>freebsd-ports@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>

Hi, 

Yes, what you have in libmap.conf appears to be correct (I'm presuming those
are the correct library versions).

I have not yet had the time to figure out why, but I had a similar build
problem, using clang in ports to rebuild libwpg first, then libvisio seems to
work.

--
Waitman Gobble
San Jose California USA
+1.5108307875


_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to