[Ham-Mac] Update on the ARRL Logbook of the World (LoTW) electronic QSLing project

[Marinus van Opzeeland]

cc, g++ or c++ all give the same error.

I noticed that there are at least 3 members on the list working on this 
stuff, so sooner or later one of us will figure it out and we can share 
it with the list.

73, Marinus - PE1LIF

Russell Finn heeft op woensdag, 4 jun 2003 om 23:06 (Europe/Amsterdam) 
het volgende geschreven:

> On Wednesday, June 4, 2003, at 01:49  PM, Marinus van Opzeeland wrote:
>> Without  making any changes yet the actual tqsl apps seem to compile 
>> pretty good as well. Using the X11 version of wxWindows from Fink's 
>> unstable tree got me as far as the linker.
>>
>> cc -O0 -g3 -Wall -I../src -I../../expat/include  -DHAVE_LIBCRYPTO=1 
>> -DSTDC_HEADERS=1 -DHAVE_MKDIR=1 -DHAVE_STRERROR=1  `wx-config 
>> --cflags`  -o tqslcert tqslcert.o crqwiz.o dxcc.o certtree.o 
>> tqslcert_prefs.o -lz -lexpat -lcrypto -L../src -ltqsllib `wx-config 
>> --libs` -lstdc++
>> ld: warning suggest use of -bind_at_load, as lazy binding may result 
>> in errors or different symbols being used
>> symbol _locale_charset used from dynamic library 
>> /sw/lib/libiconv.2.dylib(localcharset.lo) not from earlier dynamic 
>> library /sw/lib/libintl.1.dylib(localcharset.lo)
>> ld: Undefined symbols:
>> ___builtin_delete
>> operator new(unsigned long, void *)
>> ___throw
>> [snip]
>
> Without knowing anything else about what you're doing:  I notice that 
> all the undefined symbols are C++ runtime or library functions, but 
> your command line begins with "cc".  I would try using "c++" instead, 
> which should automatically link in all the necessary C++ runtime 
> libraries.  (I think the "-lstdc++" at the end of the command line is 
> not sufficient.)
>
> Good luck es 73,
> -- Russ, WA3YSW
>