The default bug view has changed. See this FAQ.

configure hangs in |running develop|

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: Justin Lebar (not reading bugmail))

Tracking

(Depends on: 1 bug)

Trunk
mozilla17
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

5 years ago
My clobber, debug Linux 64 build of the tip of m-i (4e95ccf43b6e) is currently hung at:

  Creating Python virtualenv
  New python executable in ./_virtualenv/bin/python2.7
  Also creating executable in ./_virtualenv/bin/python
  Installing setuptools............done.
  Installing pip...............done.
  Populating Python virtualenv
  running develop

We've been hung here for at least five minutes.  Top shows that python is using 100% of a CPU.
(Assignee)

Updated

5 years ago
Severity: normal → blocker
(Assignee)

Updated

5 years ago
Summary: Configure hangs in |running develop| → configure hangs in |running develop|
(Assignee)

Comment 1

5 years ago
  srcdir$ find . -name '*.pyc' | xargs rm

did not fix the problem for me.
What process(es) are sucking the cpu?
(Assignee)

Comment 3

5 years ago
/home/jlebar/code/moz/ff-inbound/debug/_virtualenv/bin/python /home/jlebar/code/moz/ff-inbound/src/other-licenses/simplejson-2.1.1/setup.py develop
(Assignee)

Comment 4

5 years ago
Looking at the environment we pass to setup.py, I see:

'LDFLAGS': '$(LDFLAGS)'
'CFLAGS': '$(CFLAGS) -DXP_UNIX'

That doesn't seem right...

Comment 5

5 years ago
Did I use the wrong braces in the configure.in patch in https://hg.mozilla.org/integration/mozilla-inbound/rev/fda9279d7031?
(Assignee)

Comment 6

5 years ago
Created attachment 644960 [details] [diff] [review]
Patch, v1

I have no idea if this is the best way to expand these variables.
(Assignee)

Updated

5 years ago
Attachment #644960 - Flags: review?(mh+mozilla)
(Assignee)

Updated

5 years ago
Blocks: 774106
Comment on attachment 644960 [details] [diff] [review]
Patch, v1

Review of attachment 644960 [details] [diff] [review]:
-----------------------------------------------------------------

::: configure.in
@@ +8801,2 @@
>    CC="${CC}" CXX="${CXX}" \
> +  CFLAGS="$(eval echo "${HOST_CFLAGS}")" CXXFLAGS="$(eval echo "${HOST_CXXFLAGS}")" \

You should just change the initial definitions at the top of configure.in to match those used for the cross-compile case.
Attachment #644960 - Flags: review?(mh+mozilla) → review-
(Assignee)

Comment 8

5 years ago
I didn't do that because jcranmer said it would cause problems:

  <jcranmer> glandium, jlebar: while "freezing" the HOST_* flags at compile time would be nice, I've found that a lot of builds break if you do it

Do you two want to duke it out?
(Assignee)

Updated

5 years ago
Assignee: nobody → justin.lebar+bug
(Assignee)

Comment 9

5 years ago
Created attachment 644966 [details] [diff] [review]
Patch, v2

jcranmer tells me I misunderstood him, so here you go.  :)
Attachment #644966 - Flags: review?(mh+mozilla)
Attachment #644966 - Flags: review?(mh+mozilla) → review+
(Assignee)

Updated

5 years ago
Attachment #644960 - Attachment is obsolete: true
(Assignee)

Comment 10

5 years ago
This is failing on buildbots with https://tbpl.mozilla.org/php/getParsedLog.php?id=13775717&tree=Mozilla-Inbound#error0 , although I don't know what that means.
(Assignee)

Comment 11

5 years ago
Landed: https://hg.mozilla.org/integration/mozilla-inbound/rev/603215dd3a5e
Then backed out due to the failure in comment 10: https://hg.mozilla.org/integration/mozilla-inbound/rev/28c7063c8cda
Then re-landed with Makefile.in fixes from glandium: https://hg.mozilla.org/integration/mozilla-inbound/rev/bfd0d06e1a78
https://hg.mozilla.org/mozilla-central/rev/bfd0d06e1a78
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Depends on: 788464
You need to log in before you can comment on or make changes to this bug.