Closed Bug 679001 Opened 13 years ago Closed 13 years ago

xpt.py is not installed by xulrunner-6.0 causing firefox-6.0 build failures

Categories

(Firefox Build System :: General, defect)

6 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 639554

People

(Reporter: superheron, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0.1) Gecko/20110815 Firefox/5.0.1
Build ID: 20110729232145

Steps to reproduce:

I built xulrunner-6.0, then I built firefox-6.0 on top of it.
I'm using Exherbo Linux 3.0.1 x86_64 with gcc 4.5.3.


Actual results:

firefox-6.0 build failed due to xpt.py absence (i.e. No such file or directory), probably not installed by xulrunner-6.0.
Build log is at http://paste.pocoo.org/show/458737/


Expected results:

firefox-6.0 build succeeded.
Component: General → Build Config
QA Contact: general → build.config
I'm surprised that we're not just using xpt.py out of the source directory: khuey do you know why we're using it from a build directory? This is probably something we should fix quickly if it affects Linux distros, which sometimes/often use --with-libxul-sdk builds.
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #1)
> I'm surprised that we're not just using xpt.py out of the source directory:
> khuey do you know why we're using it from a build directory? This is
> probably something we should fix quickly if it affects Linux distros, which
> sometimes/often use --with-libxul-sdk builds.

We use xpt.py from the SDK, and as far as I can tell, a make install'ed SDK does contain xpt.py.
401 XPIDL_LINK = $(PYTHON) $(LIBXUL_DIST)/sdk/bin/xpt.py link

We're installing it in the right place, just not packaging it in the sdk I guess :-/
Ah, that's bug 639554
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
(So it *is* packaged in the sdk, not in the sdk that you get with make install ; and that's fixed in 7.0)
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.