debug flag, I was able to quickly resolve the problem that has been bugging
me for weeks.
I have had the debug flag on before. Without any error messages, I had to
do binary search to find the class that was causing the problem. I got the
code to compile by excluding one class, but still did not know why. Now with
the debug flag off, I found that there was one undefined function in it. I
fixed it and it compiles happily with or without the debug flag.
Does anyone from QSSL want to comment on this? When can we expect a fix to
"John Nagle" <email@example.com> wrote in message
Ah. Unpack that tarball and try
and it works fine, producing an error message.
QCC -g main.cc
to generate debug info. You'll get a junk "a.out" file,
with no error messages. So this problem is somehow
involved with the generation of debug information.
The recursive build system adds quite a few options to
the qcc command line, so it's better to try this with
a cleaner situation.
Chris McKillop wrote:
John Nagle <firstname.lastname@example.org> wrote:
Any word on this? I'm currently programming by using
"nm" to read out all the undefined symbols and checking
them by hand when the QNX "ld" fails. This is becoming
If it's the Free Software Foundation's problem, let
me know, and I'll bug one of the GNU developers. I'm
still not clear on whether QSSL or FSF maintains the
QNX "ld". Thanks.
I just tried your code on a 6.2.0 PE, 6.2.1 PE and 6.2.0 NC. Now, I am
using our recursive build system, you can get the sources here:
In all cases it compiles fine and fails to link. Gives proper warning
the lack of the missing function. If you get that tarball and run make
does it behave for you?