Closed Bug 1229495 Opened 8 years ago Closed 8 years ago

Build error: 'no preprocessor directives found' in 'suite/locales/en-US/searchplugins/duckduckgo.xml'


(SeaMonkey :: Build Config, defect)

Not set


(seamonkey2.42 fixed)

Tracking Status
seamonkey2.42 --- fixed


(Reporter: ssitter, Assigned: philip.chee)




(1 file)

Originally reported in Bug 1229419 Comment 3:

> ...'c:/seamonkey/comm-central/suite/locales/en-US/searchplugins/duckduckgo.xml' -o '../../dist/bin/searchplugins/duckduckgo.xml'
> rm -f '../../dist/bin/searchplugins/wikipedia.xml'
> Traceback (most recent call last):
>   File "c:\mozilla-build\python\Lib\", line 162, in _run_module_as_main
>     "__main__", fname, loader, pkg_name)
>   File "c:\mozilla-build\python\Lib\", line 72, in _run_code
>     exec code in run_globals
>   File "c:\seamonkey\comm-central\mozilla\python\mozbuild\mozbuild\action\", line 18, in <module>
>     main(sys.argv[1:])
>   File "c:\seamonkey\comm-central\mozilla\python\mozbuild\mozbuild\action\", line 14, in main
>     pp.handleCommandLine(args, True)
>   File "c:\seamonkey\comm-central\mozilla\python\mozbuild\mozbuild\", line 483, in handleCommandLine
>     self.processFile(input=input, output=out)
>   File "c:\seamonkey\comm-central\mozilla\python\mozbuild\mozbuild\", line 388, in processFile
>     self.failUnused(
>   File "c:\seamonkey\comm-central\mozilla\python\mozbuild\mozbuild\", line 332, in failUnused
>     raise Preprocessor.Error(fake, msg, None)
> mozbuild.preprocessor.Error: ('c:/seamonkey/comm-central/suite/locales/en-US/searchplugins/duckduckgo.xml', None, 'no preprocessor directives found', None)
> c:/seamonkey/comm-central/mozilla/config/ recipe for target '../../dist/bin/searchplugins/duckduckgo.xml' failed
> mozmake[4]: *** [../../dist/bin/searchplugins/duckduckgo.xml] Error 1
> mozmake[4]: *** Deleting file '../../dist/bin/searchplugins/duckduckgo.xml'
> mozmake[4]: *** Waiting for unfinished jobs....

This looks like fallout from Bug 1228467 - Make the preprocessor error out for "no preprocessing directives".

If I investigated it correct the files are read from searchplugins/list.txt <> added to PP_TARGETS in

Maybe this can be switched to a target without preprocessing, after ensuring that none of the existing localizations uses preprocessing in the searchplugins files.
Version: Trunk → SeaMonkey 2.42 Branch
So this is why there were no nightlies on December 1! The fact that there were no nightlies even on platforms which had them the day before (i.e. L32, L64 and Mac) makes me think that either there is yet another blocker born on the same day, or this is a platform-agnostic bug.

FTR: From comment #0 it can be seen that the bug was seen on Windows; which particular Windows architecture is less evident.
Severity: normal → blocker
OS: Unspecified → All
Hardware: Unspecified → All
Version: SeaMonkey 2.42 Branch → Trunk
I'm setting the dependency on the assumption that ssitter guessed it right in comment #0. Feel free to set if differently if another culprit is found.
Blocks: 1228467
A patch to silence the SeaMonkey build error was added to Bug 1229419 instead of adding it here.
Firefox and Thunderbird have had this bit for ages, but somehow we never bothered to turn off the warnings until now when glandium made preprocessor warnings errors instead.

(I'll file separate bugs for the DOM Inspector and Chatzilla.
Assignee: nobody → philip.chee
Attachment #8694921 - Flags: review?(iann_bugzilla)
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.42
Comment on attachment 8694921 [details] [diff] [review]
Silence complaints about missing preprocessor directives in search plugins. r=IanN

Carrying forward r+ from Bug 1229419
Attachment #8694921 - Attachment description: Silence complaints about missing preprocessor directives in search plugins. → Silence complaints about missing preprocessor directives in search plugins. r=IanN
Attachment #8694921 - Flags: review?(iann_bugzilla) → review+
You need to log in before you can comment on or make changes to this bug.