Closed Bug 221126 Opened 21 years ago Closed 8 years ago

Warnings in unix_rand.c


(NSS :: Libraries, defect, P3)



(Not tracked)



(Reporter: timeless, Unassigned)


(Blocks 1 open bug)


(Whiteboard: [build_warning])


(1 file)

In file included from /swap/BEOS/mozilla/security/nss/lib/freebl/sysrand.c:36:
 In function `RNG_SystemInfoForRNG':
831: warning: assignment from incompatible pointer type
840: warning: implicit declaration of function `gethostname'
Attachment #132580 - Flags: review?(wchang0222)
QA Contact: bishakhabanerjee → jason.m.reid
QA Contact: jason.m.reid → libraries
Priority: -- → P3
Version: unspecified → 3.9
Attachment #132580 - Flags: superreview-
Comment on attachment 132580 [details] [diff] [review]
remove incorrect const marking

I think the include part of the patch is OK. But the second part if not. If you are going to change the type of cp, you need to change all the casts, and the environ declaration. I'm not sure if that will work on all Unix platforms.
Whiteboard: [build_warning]
Blocks: buildwarning
I don't see any warning on linux. But the warning might be specific to BeOS due to #ifdef. But I would suggest closing this one and opening new one if we find some warnings in BeOS as this is a bug not tortoise (already lifespan of 8 years).
It looks like incompatible pointer type issue was fixed in Bug 265369.

(See )

Does the code still warn about the implicit declaration?
Flags: needinfo?(timeless)
bug 265369 seems to have resolved one of two warnings for this file.

I don't have BeOS particularly handy, but I'm pretty sure that it would still warn about the implicit declaration. There certainly haven't been any changes to the file that would resolve it.

I don't see any includes in the relevant directory for the file.
Flags: needinfo?(timeless)
timeless, do you know if anyone is maintaining NSS for BeOS or Haiku? Can we WONTFIX open BeOS bugs?
Flags: needinfo?(timeless)
I do not know. I haven't worked on Mozilla at all in 5 years...
Assignee: timeless → nobody
Flags: needinfo?(timeless)
Thanks. I'm going to close this bug because the warning was apparently fixed in 2005 by bug 265369, according to comment 5. :)
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.