Open Menu
Close Menu
Apple
Shopping Bag
Apple
Mac
iPad
iPhone
Watch
TV
Music
Support
Search apple.com
Shopping Bag
Lists
Open Menu
Close Menu
Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists
Problems moving to 2.1
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Problems moving to 2.1
Subject
:
Problems moving to 2.1
From: Chris Griffin <
email@hidden
>
Date: Fri, 12 Aug 2005 15:45:40 -0700
I have a project that worked fine in 1.5. I am now using 2.1 and making some changes. I have a library that I include and it is now complaining of undefined symbols:
std::__default_alloc_template<true, 0>::deallocate(void*, unsigned long)
std::__default_alloc_template<true, 0>::allocate(unsigned long)
std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_S_create(unsigned long, std::allocator<char> const&)
Isn't that all part of the C++ library? I have been using <string>, <vector> and such for awhile now with no errors. It's only when I started calling this library that I get the undefined errors.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Follow-Ups
:
Re: Problems moving to 2.1
From:
Eric Albert <email@hidden>
Prev by Date:
Issues and questions about Xcode 2.1
Next by Date:
Question about a gcc 4 warning
Previous by thread:
Re: Issues and questions about Xcode 2.1
Next by thread:
Re: Problems moving to 2.1
Index(es):
Date
Thread