Closed Bug 923621 Opened 11 years ago Closed 11 years ago

mozbuild.frontend.reader.SandboxValidationError: Reference to a file that doesn't exist in CSRCS (icalderivedparameter.c) in calendar/libical/src/libical

Categories

(MailNews Core :: Build Config, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Unassigned)

Details

Seen since some m-c bugs recently landed:

Traceback (most recent call last):
  File "./config.status", line 961, in <module>
    config_status(**args)
  File "/builds/slave/tb-c-cen-lx-ntly-0000000000000/build/mozilla/build/ConfigStatus.py", line 126, in config_status
    summary = backend.consume(definitions)
  File "/builds/slave/tb-c-cen-lx-ntly-0000000000000/build/mozilla/python/mozbuild/mozbuild/backend/base.py", line 188, in consume
    for obj in objs:
  File "/builds/slave/tb-c-cen-lx-ntly-0000000000000/build/mozilla/python/mozbuild/mozbuild/frontend/emitter.py", line 77, in emit
    for o in self.emit_from_sandbox(out):
  File "/builds/slave/tb-c-cen-lx-ntly-0000000000000/build/mozilla/python/mozbuild/mozbuild/frontend/emitter.py", line 134, in emit_from_sandbox
    % (symbol, src, sandbox['RELATIVEDIR']))
mozbuild.frontend.reader.SandboxValidationError: Reference to a file that doesn't exist in CSRCS (icalderivedparameter.c) in calendar/libical/src/libical
configure: error: /builds/slave/tb-c-cen-lx-ntly-0000000000000/build/mozilla/configure failed for mozilla
The issue is in these files:

http://mxr.mozilla.org/comm-central/source/calendar/libical/src/libical/moz.build
http://mxr.mozilla.org/comm-central/source/calendar/libical/src/libical/Makefile.in

The Makefile.in is generating .c files from .c.in files, hence at generation time, these are listed in CSRCS but aren't available.

If I take them out of CSRCS, then the configure completes but link fails. What's the bit of magic I'm missing?
I believe we put them back in CSRCS in the Makefile.
Thanks, attempted work around is here:

https://hg.mozilla.org/comm-central/rev/56a6ff586cda

(works for me locally).
Yep, that's the correct fix for now. Thanks!
Also had to fix windows:

https://hg.mozilla.org/comm-central/rev/66a1ea02542f
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.