Closed Bug 322992 Opened 19 years ago Closed 19 years ago

--enable-calendar fails on latest CVS builds

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mvanier, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060109 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060109 SeaMonkey/1.5a The current CVS build of seamonkey fails when I add the --enable-calendar configure option. My full list of options follows: ac_add_options --enable-default-toolkit=gtk2 ac_add_options --enable-xft ac_add_options --disable-freetype2 ac_add_options --with-pthreads ac_add_options --enable-application=suite ac_add_options --enable-svg ac_add_options --enable-calendar If I remove the --enable-calendar option, the program compiles cleanly. With the option, I get this: make[4]: *** No rule to make target `/home/mvanier/src/core/mozilla/seamonkey/mozilla/calendar/Makefile.in', needed by `calendar/Makefile'. Stop. Reproducible: Always Steps to Reproduce: 1. Set up a .mozconfig file for seamonkey including the option "ac_add_options --enable-calendar". 2. Do "make -f client.mk build" 3. Actual Results: Everything compiles cleanly, until I get: make[4]: *** No rule to make target `/home/mvanier/src/core/mozilla/seamonkey/mozilla/calendar/Makefile.in', needed by `calendar/Makefile'. Stop. Expected Results: The program should compile cleanly all the way. Removing the offending option fixes the problem, but then the calendar isn't compiled.
It looks to me like you didn't pull the calendar sources: what MOZ_CO_PROJECTs are you pulling? (needs to be at least MOZ_CO_PROJECT=suite,calendar)
You're right -- I didn't include "calendar" in the MOZ_CO_PROJECT list, just "suite". My bad -- sorry. I'm compiling it now and all seems fine.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.