Closed Bug 302992 Opened 19 years ago Closed 8 years ago

--enable-crypto dependencies are incomplete

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mbockelkamp, Unassigned)

Details

Attachments

(1 file)

My MinGW build with --enable-crypto failed while creating mime.dll because of
references to an unknown functions "mime_crypto_stamped_p" and
"mime_set_crypto_stamp". I cannot repeat the exact error message. This can be
fixed with two "#include"s. Patch follows. Can someone confirm this issue?
Attached patch PatchSplinter Review
This is current trunk build?
I did the checkout today, about 4 hours ago.
Assignee: dveditz → nobody
Blocks: mingw
Component: Security → MailNews: MIME
Product: Mozilla Application Suite → Core
QA Contact: seamonkey
Version: unspecified → Trunk
Why/how does this patch help? Both files include mimemoz2.h which already
includes mimei.h
Component: MailNews: MIME → Build Config
QA Contact: build-config
I notice mimemoz2.h contains

 #ifdef XP_UNIX
 #undef Bool
 #endif

right before including mimei.h -- perhaps the real fix is to add mingw to that
ifdef (assuming it has unix-like headers).
This sounds like the problem that occurs when the build is first made without
--enable-crypto then --enable-crypto is added.  Unfortunately, changing that
flag doesn't cause certain parts of the tree (the ones that rely upon
BUILD_SMIME, iirc) to be rebuilt.

BTW, My cross-compiled mingw build worked fine with a current tree.
No longer blocks: mingw
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: MinGW build failure in mime.dll → --enable-crypto dependencies are incomplete
This happened to me after changing .mozconfig, but also after a "make clean" and
manually deleting the obj dir.

How does this "#undef Bool" influence the following #include?
To think there was a time when crypto had to be enabled in configure. Anyway, --enable-crypto no longer exists, so this bug is invalid.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: