Build failing with ../config/autoconf.mk:668: ../src/config/baseconfig.mk: No such file or directory

RESOLVED FIXED in mozilla17

Status

()

Core
Build Config
--
blocker
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Justin Lebar (not reading bugmail), Assigned: glandium)

Tracking

Trunk
mozilla17
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

5 years ago
Linux x64 clobber build, tip of m-c (0a17cde2a4b6) is failing for me during configure:

make[5]: Entering directory `/home/jlebar/code/moz/ff-git/debug/config'
../config/autoconf.mk:668: ../src/config/baseconfig.mk: No such file or directory
Makefile:53: ../src/config/config.mk: No such file or directory
Makefile:58: ../src/config/rules.mk: No such file or directory
make[5]: *** No rule to make target `../src/config/rules.mk'.  Stop.
(Reporter)

Updated

5 years ago
Severity: normal → blocker
Likely due to bug 774032.
Blocks: 774032
How is your mozconfig?
Created attachment 649034 [details] [diff] [review]
Make top_srcdir absolute in config.status

This should work as a workaround, provided that pwd returns a msys path on windows.

I however would like to fix this more nicely.
Don't rely on pwd to return an msys path on Windows. See bug 777798.
(Reporter)

Comment 5

5 years ago
(In reply to Mike Hommey [:glandium] from comment #2)
> How is your mozconfig?

. $topsrcdir/browser/config/mozconfig

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../debug
ac_add_options --srcdir=../src

ac_add_options --enable-trace-malloc
ac_add_options --enable-debug
ac_add_options --disable-optimize
ac_add_options --with-ccache

mk_add_options MOZ_MAKE_FLAGS="-j16"
ac_add_options --enable-application=browser
(Reporter)

Comment 6

5 years ago
Oh, I see how that srcdir is getting in there now.

Maybe I don't need srcdir anymore; it was to make ccache happier caching object files between checkouts, but perhaps our build or ccache has become smarter since then.
(Reporter)

Comment 7

5 years ago
As expected, removing the explicit srcdir fixes the problem for me.  I'm still not sure if it's doing anything good for me.
FWIW, this happens if you either build with a relative --srcdir like you did, or just run configure directly, from a relative directory.
Considering this doesn't affect building with make -f client.mk under "normal" circumstances, I'll leave bug 774032 in. Actual fix coming next.
Assignee: nobody → mh+mozilla
Created attachment 649078 [details] [diff] [review]
Fix ConfigStatus.py for the case where top_srcdir is a path relative to topobjdir.

It turns out the unittest was completely wrong for testing srcdir, so this bug came through while it shouldn't have :-/
Attachment #649078 - Flags: review?(ted.mielczarek)
Attachment #649034 - Attachment is obsolete: true
OS: Linux → All
Hardware: x86_64 → All
Attachment #649078 - Flags: review?(ted.mielczarek) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/d83147d64e06
Target Milestone: --- → mozilla17
https://hg.mozilla.org/mozilla-central/rev/d83147d64e06
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
I hope that this may fix the l10n repacks, too, need to see in the next nightlies.
I pushed a followup to unbreak pymake (and hopefully not rebreak anything else).

https://hg.mozilla.org/mozilla-central/rev/c8d94fe7506a
You need to log in before you can comment on or make changes to this bug.