Closed
Bug 182425
Opened 22 years ago
Closed 22 years ago
Mach-O Build: Case sensitivity issues
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: slogan, Assigned: slogan)
Details
Attachments
(2 files)
2.12 KB,
patch
|
netscape
:
review+
slogan
:
superreview+
|
Details | Diff | Splinter Review |
768 bytes,
patch
|
netscape
:
review+
sfraser_bugs
:
superreview+
|
Details | Diff | Splinter Review |
Building Mach o on OS X, no matter what I did, I kept dying in
intl/locale/src/nsLocaleService.cpp on line 56: script.h: No such file or directory.
#if defined( XP_MAC ) || defined( XP_MACOSX )
...
#include <script.h>
...
#endif
References to <[sS]cript.h> are found in a few source files in the tree, almost
always in macos-only files, which I would guess are only built in CFM builds or
on OS 9, or wrapped by #ifdef XP_MAC (but never XP_MACOSX, except in this case
in more generic platform independent sources). In most cases, the directive
spells the file with initial caps, i.e. <Script.h>. I failed to build
intl/ocale/src/mac/nsMacLocale.cpp as well.
I couldn't find script.h anywhere on my system. Script.h, however, is located in
a few, for example, somewhere below
/System/Library/Frameworks/CoreServices.framework.
I followed instructions for setting up Mach o builds, precisely.
My tree is on a native OS X Unix formatted drive. I suspected the problem is
that I'm running into an issue with case-sensitivity. To test this, I re-typed
the lines to read #include <Script.h> and my problem cleared up. If this is in
fact the problem, I suspect that we need to make sure that case is correctly
specified for include files from here on out so that people don't waste a day
chasing their tails like I did.
Patch to follow for the changes I had to make. Filing against build config in
case there is some magic ignore case flag that can be passed to gcc.
Updated•22 years ago
|
Attachment #107847 -
Flags: review+
Comment on attachment 107847 [details] [diff] [review]
some h file changes needed for UFS builds
was given an sr= by sfraser. applying it now.
Attachment #107847 -
Flags: superreview+
Comment 3•22 years ago
|
||
have fun with that ufs formatted drive ;) you'll be in a world of hurt for just
about everything. ;) really, stick to HFS+.
Checked in files for first patch, leaving open in case there are more files to
deal with.
With a tree on HFS+, still have the problem, probably because my dev tools are
installed on a UFS drive (which is how I set up my system).
Attachment #107926 -
Flags: review?(seawood)
Updated•22 years ago
|
Attachment #107926 -
Flags: review?(seawood) → review+
Updated•22 years ago
|
Attachment #107926 -
Flags: superreview+
since the build now builds cleaning, closing this one.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•