Closed
Bug 1219552
Opened 9 years ago
Closed 7 years ago
Source's |configure| step is failing due to using glibc.i686 under x86-64 mock env.
Categories
(SeaMonkey :: Release Engineering, defect)
SeaMonkey
Release Engineering
Tracking
(firefox44 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox44 | --- | affected |
People
(Reporter: ewong, Assigned: ewong)
References
Details
Attachments
(3 files, 3 obsolete files)
917 bytes,
patch
|
Details | Diff | Splinter Review | |
2.05 KB,
patch
|
Details | Diff | Splinter Review | |
3.52 KB,
patch
|
Details | Diff | Splinter Review |
SeaMonkey's 2.39b1's source step failed with: checking NSPR selection... source-tree checking for YASM assembler... checking for yasm... yasm checking for application to build... ../suite checking if app-specific confvars.sh exists... /builds/slave/rel-c-beta-source/comm-beta/mozilla/../suite/confvars.sh checking for gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0... Package gtk+-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-2.0' found Package gtk+-unix-print-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-unix-print-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-unix-print-2.0' found Package glib-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `glib-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'glib-2.0' found Package gobject-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gobject-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gobject-2.0' found Package gdk-x11-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gdk-x11-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gdk-x11-2.0' found ------ config.log ------ configure: error: Library requirements (gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. configure:14556: /usr/bin/ccache /tools/gcc-4.7.3-0moz1/bin/gcc -o conftest -gdwarf-2 -DYUV_DISABLE_ASM=1 -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -lpthread -DYUV_DISABLE_ASM=1 -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id conftest.c -ldl 1>&5 configure:14588: checking for malloc.h configure:14624: checking whether malloc_usable_size definition can use const argument configure:14635: /usr/bin/ccache /tools/gcc-4.7.3-0moz1/bin/gcc -c -gdwarf-2 -DYUV_DISABLE_ASM=1 -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread conftest.c 1>&5 configure:14629:26: error: conflicting types for 'malloc_usable_size' In file included from configure:14627:0: /usr/include/malloc.h:143:15: note: previous declaration of 'malloc_usable_size' was here configure: failed program was: I believe we need to get the source step using tooltool.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8680481 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 2•9 years ago
|
||
Assignee | ||
Comment 3•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Summary: Source's |configure| step is failing due to using /tools/gcc-4.7.3-0moz1. → Source's |configure| step is failing due to using glibc.i686 under x86-64 mock env.
Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8680481 -
Attachment is obsolete: true
Attachment #8680481 -
Flags: review?(bugspam.Callek)
Attachment #8681151 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 5•9 years ago
|
||
Attachment #8680482 -
Attachment is obsolete: true
Attachment #8680482 -
Flags: review?(bugspam.Callek)
Attachment #8681152 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 6•9 years ago
|
||
Comment on attachment 8681151 [details] [diff] [review] [configs] fix source's configure step. (v2) [checked-in] Pushed to buildbot-configs: https://hg.mozilla.org/build/buildbot-configs/rev/a05060dc6518
Attachment #8681151 -
Attachment description: [configs] fix source's configure step. (v2) → [configs] fix source's configure step. (v2) [checked-in]
Assignee | ||
Comment 7•9 years ago
|
||
Comment on attachment 8681151 [details] [diff] [review] [configs] fix source's configure step. (v2) [checked-in] Backed out: https://hg.mozilla.org/build/buildbot-configs/rev/4a193273d8f4 Reason: Apparently what I had manually patched on the master != what I had locally.
Attachment #8681151 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 8•9 years ago
|
||
Attachment #8681151 -
Attachment is obsolete: true
Attachment #8693144 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 9•9 years ago
|
||
Comment on attachment 8693144 [details] [diff] [review] [configs] fix source's configure step. (v3) [checked-in] Pushed to buildbot-configs: https://hg.mozilla.org/build/buildbot-configs/rev/494fd3aee543
Attachment #8693144 -
Attachment description: [configs] fix source's configure step. (v3) → [configs] fix source's configure step. (v3) [checked-in]
Assignee | ||
Comment 10•8 years ago
|
||
Comment on attachment 8681152 [details] [diff] [review] [custom] fix source's configure step. (v2) [checked-in] Pushed to buildbotcustom: https://hg.mozilla.org/build/buildbotcustom/rev/19f2e193d1db
Attachment #8681152 -
Attachment description: [custom] fix source's configure step. (v2) → [custom] fix source's configure step. (v2) [checked-in]
Assignee | ||
Updated•7 years ago
|
Attachment #8681152 -
Flags: review?(bugspam.Callek)
Assignee | ||
Updated•7 years ago
|
Attachment #8693144 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 11•7 years ago
|
||
With both patches checked in and running, unsetting review flag (w/ Callek's approval) and closing.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•