Closed Bug 776537 Opened 8 years ago Closed 8 years ago

configure hangs in |running develop|

Categories

(Firefox Build System :: General, defect, blocker)

x86_64
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED
mozilla17

People

(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)

References

(Depends on 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

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.
Severity: normal → blocker
Summary: Configure hangs in |running develop| → configure hangs in |running develop|
  srcdir$ find . -name '*.pyc' | xargs rm

did not fix the problem for me.
What process(es) are sucking the cpu?
/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
Looking at the environment we pass to setup.py, I see:

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

That doesn't seem right...
Did I use the wrong braces in the configure.in patch in https://hg.mozilla.org/integration/mozilla-inbound/rev/fda9279d7031?
Attached patch Patch, v1 (obsolete) — Splinter Review
I have no idea if this is the best way to expand these variables.
Attachment #644960 - Flags: review?(mh+mozilla)
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-
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: nobody → justin.lebar+bug
Attached patch Patch, v2Splinter Review
jcranmer tells me I misunderstood him, so here you go.  :)
Attachment #644966 - Flags: review?(mh+mozilla)
Attachment #644966 - Flags: review?(mh+mozilla) → review+
Attachment #644960 - Attachment is obsolete: true
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.
https://hg.mozilla.org/mozilla-central/rev/bfd0d06e1a78
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.