Closed Bug 25105 Opened 25 years ago Closed 25 years ago

Some BSD platforms do not have ENOLINK

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Platform:
x86
FreeBSD
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: cls, Assigned: shaver)

References

(
URL
)

Details

A couple of our tinderboxes on the SeaMonkey-Ports page have been dying for the past week with 'ENOLINK' undefined errors. ENOLINK is used in nsresultForError() in xpcom/io/nsLocalFileUnix.h. ENOLINK appears to be srv4 specific. I don't know what the proper method to check for ENOLINK under *BSD would be but here's are links to the FreeBSD manpages on symlink & stat: http://www.FreeBSD.org/cgi/man.cgi?query=symlink&apropos=0&sektion=0&manpath=FreeBSD+3.4-RELEASE&format=html http://www.FreeBSD.org/cgi/man.cgi?query=stat&apropos=0&sektion=0&manpath=FreeBSD+3.4-RELEASE&format=html
mike, can you give this your loving?
ENOLINK is probably not what I want. I'm on it.
Assignee: dougt → shaver
Fixed by Pascal Hofstee & sspitzer a few days ago.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.