After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 122856 - Compilation fails on Darwin
Compilation fails on Darwin
Status: RESOLVED INCOMPLETE
Product: eel
Classification: Deprecated
Component: general
2.14.x
Other Mac OS
: Urgent normal
: 2.14.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-09-21 06:37 UTC by Jerry Talkington
Modified: 2006-10-06 12:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
patch for darwin (1019 bytes, patch)
2003-09-21 06:38 UTC, Jerry Talkington 		needs-work Details | Review
Checks for crt_externs.h and _NSGetEnviron, and cleans up some tests (3.01 KB, patch)
2003-10-11 16:23 UTC, Jerry Talkington 		none Details | Review

Description Jerry Talkington 2003-09-21 06:37:40 UTC 
Apple's unistd.h doesn't have environ declared (nor is it declared in any
other headers,) so a few extra lines of code have to be added to any file
that use it.
Comment 1 Jerry Talkington 2003-09-21 06:38:21 UTC 
Created attachment 20149 [details] [review]
patch for darwin
Comment 2 Jerry Talkington 2003-10-11 16:22:01 UTC 
That patch sucks.  Here is a new one.
Comment 3 Jerry Talkington 2003-10-11 16:23:26 UTC 
Created attachment 20649 [details] [review]
Checks for crt_externs.h and _NSGetEnviron, and cleans up some tests
Comment 4 Christian Neumair 2006-03-18 11:48:57 UTC 
Thanks for your bug report and your patch, and sorry for the late response!

Maybe you could submit the patch to the nautilus mailing list [1] for review?

[1] http://mail.gnome.org/mailman/listinfo/nautilus-list
Comment 5 Alexander Larsson 2006-08-08 14:53:38 UTC 
This doesn't apply anymore (the egg file is deleted). Is it still needed?
Comment 6 André Klapper 2006-10-06 12:38:29 UTC 
Closing this bug report as no further information has been provided. Jerry, if this still applies, please do reopen this bug report.
Thanks in advance!