Sorry, the actual message is "identifier not found", "undefined symbol"
was a product of my faulty memory.
I understand that noone else has seen this problem, but it's faulty
logic to suggest that these files don't need to include stdlib.h.. if
it's compiling it just means that stdlib.h has been included by another
header.
Robert Smith.
On 03/16/2015 11:08 AM, Ross Finlayson wrote:
But I don't think it's unreasonable for files to include the headers
that define the symbols they use so maybe worth adding stdlib.h to
the files that need it?
But I have no evidence that these file 'need' to #include 'stdlib.h'.
If they did, then they wouldn't *compile*.
'Undefined symbol' errors are problems that occur during *linking* -
which has nothing to do with #include files.
Once again, nobody else has reported the problem that you claim to be
seeing.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
