wstring and gcc

wstring and gcc

[andy]

I'm running gcc 3.2 on a redhat linux box.

this simple code :
int main()
{
wstring foo;
printf("%s\n",foo.c_str());
return 0;
}

produces the following link error:
"
/tmp/cceNYHXk.o: In function `main':
/tmp/cceNYHXk.o(.text+0x18): undefined reference to
`std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::basic_string[in-charge]()'
/tmp/cceNYHXk.o(.text+0x23): undefined reference to
`std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::c_str() const'
/tmp/cceNYHXk.o(.text+0x3e): undefined reference to
`std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::~basic_string [in-charge]()'
/tmp/cceNYHXk.o(.text+0x51): undefined reference to
`std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::~basic_string [in-charge]()'
collect2: ld returned 1 exit status"

since gcc 3.2 is in my home directory, the command line to build the app is
as follows:
/home/andy/tools3.2/H-i686-pc-linux-gnu/bin/gcc -o tstapp test.cpp -static
-lstdc++

Any help in resolving this is greatly appreciated
Andy

Re: wstring and gcc

[andy]

No responses so far. Nobody knows or wrong list?
If the latter, where should I post it ?
Thx
Andy

> I'm running gcc 3.2 on a redhat linux box.
> 
> this simple code :
> int main()
> {
> wstring foo;
> printf("%s\n",foo.c_str());
> return 0;
> }
> 
> produces the following link error:
> "
> /tmp/cceNYHXk.o: In function `main':
> /tmp/cceNYHXk.o(.text+0x18): undefined reference to
> `std::basic_string<wchar_t, std::char_traits<wchar_t>,
> std::allocator<wchar_t> >::basic_string[in-charge]()'
> /tmp/cceNYHXk.o(.text+0x23): undefined reference to
> `std::basic_string<wchar_t, std::char_traits<wchar_t>,
> std::allocator<wchar_t> >::c_str() const'
> /tmp/cceNYHXk.o(.text+0x3e): undefined reference to
> `std::basic_string<wchar_t, std::char_traits<wchar_t>,
> std::allocator<wchar_t> >::~basic_string [in-charge]()'
> /tmp/cceNYHXk.o(.text+0x51): undefined reference to
> `std::basic_string<wchar_t, std::char_traits<wchar_t>,
> std::allocator<wchar_t> >::~basic_string [in-charge]()'
> collect2: ld returned 1 exit status"
> 
> since gcc 3.2 is in my home directory, the command line to build the app is
> as follows:
> /home/andy/tools3.2/H-i686-pc-linux-gnu/bin/gcc -o tstapp test.cpp -static
> -lstdc++
> 
> Any help in resolving this is greatly appreciated
> Andy
> 

Re: wstring and gcc

[Gokhan Kisacikoglu]

This did not work for me either;

#include <string>

int main()
{
    std :: wstring foo;
    return 0;
}

%> g++ -o tt tt.cpp
ld32: ERROR   33 : Unresolved text symbol "std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string[in-charge]()" -- 1st referenced by /tmp/ccHkNfJj.o.
        Use linker option -v to see when and which objects, archives and
dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::~basic_string
[in-charge]()" -- 1st referenced by /tmp/ccHkNfJj.o.
        Use linker option -v to see when and which objects, archives and
dsos are loaded.  
ld32: INFO    152: Output file removed because of error.
collect2: ld returned 2 exit status


What's that [in-charge] mean?

Gokhan

Re: wstring and gcc

[andy]

I got it to work.Basicaly, I just needed to enable wchar support in
libstdc++.
Here's what I ended up doing:
-Built and installed the latest version of glibc. That in and of itself,is a
separate and painful adventure:-)

-Built gcc3.2 
When you build gcc,normally you'd have a directory called build-gcc or
something, where the configure script puts all the makefiles . As part of
gcc full build process,it builds the libstdc++-v3 library and puts it in a
platform specific directory( in my case it's called i686-pc-linux-gnu)
Inside libstdc++-v3 directory there's a file called config.h
I added the following definitions to it:
#define _GLIB_CPP_USE_WCHAR_T 1
#define _GLIB_CPP_HAVE_WCHAR_T  1

-Make clean and make install inside libstdc++-v3 directory
There were some compile errors  in the file libstdc++-v3/include/cwchar
There is a whole mess of #undefs that I had to comment out
starts with #undef btowc
and ends with #undef wscanf

Below that, there's a bunch of "using::xxx" of the functions undef'd above-
commented that out too.
Then, there's a routine wcschr that  needs to read:
{return wcschr(const_cast<wchar_t*>(--p),--c));} otherwise I got a compile
error.
I think that's it

Now the example I initially quoted builds and runs fine.
I think the reason for all this mess is that the configure script assumed
that my environment does not support wchar.
Maybe I did it in a boneheaded brute force kind of a way - any suggestions
how to achieve the same result in a more elegant fashion, are welcom

HTH
Andy


On 9/30/02 8:16 AM, "Gokhan Kisacikoglu"  wrote:

> This did not work for me either;
> 
> #include <string>
> 
> int main()
> {
>   std :: wstring foo;
>   return 0;
> }
> 
> %> g++ -o tt tt.cpp
> ld32: ERROR   33 : Unresolved text symbol "std::basic_string<wchar_t,
> std::char_traits<wchar_t>, std::allocator<wchar_t>
>> ::basic_string[in-charge]()" -- 1st referenced by /tmp/ccHkNfJj.o.
>       Use linker option -v to see when and which objects, archives and
> dsos are loaded. 
> ld32: ERROR   33 : Unresolved text symbol "std::basic_string<wchar_t,
> std::char_traits<wchar_t>, std::allocator<wchar_t> >::~basic_string
> [in-charge]()" -- 1st referenced by /tmp/ccHkNfJj.o.
>       Use linker option -v to see when and which objects, archives and
> dsos are loaded. 
> ld32: INFO    152: Output file removed because of error.
> collect2: ld returned 2 exit status
> 
> 
> What's that [in-charge] mean?
> 
> Gokhan

Re: wstring and gcc

[Gokhan Kisacikoglu]

andy wrote:
> 
> I got it to work.Basicaly, I just needed to enable wchar support in
> libstdc++.


Does this mean you can either use the wide or normal characters, or
simply it is an configuration issue to support them both?

Gokhan

Re: wstring and gcc

[andy]

The wide char support is determined by the system, I believe.
The configure script looks for wchar support in the system headers and turns
off the libc++ macros if it doesn't find it  there.
In my particular case, I'm on a machine with a rather old kernel and I
installed gcc3 in my home directory and not in /usr
So maybe a combination of the above resulted in the problem
Andy


On 10/3/02 10:20 AM, "Gokhan Kisacikoglu"  wrote:

> andy wrote:
>> 
>> I got it to work.Basicaly, I just needed to enable wchar support in
>> libstdc++.
> 
> 
> Does this mean you can either use the wide or normal characters, or
> simply it is an configuration issue to support them both?
> 
> Gokhan