Bug 193101 - Cannot get www/chromium work
Summary: Cannot get www/chromium work
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-chromium (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-28 19:25 UTC by gja822
Modified: 2018-01-12 17:18 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gja822 2014-08-28 19:25:07 UTC
uname: FreeBSD 94.180.117.72 9.3-RELEASE FreeBSD 9.3-RELEASE #5 r270286M amd64
kern.ipc.shm_allow_removed: 1

With chromium-37.0.2062.94 and some earlier versions I can compile, but what I get doesn't work. In gdb session it says:
(gdb) r
Starting program: /usr/local/share/chromium/chrome 
[New Thread 815c07400 (LWP 101407)]
[New Thread 815f2b000 (LWP 101347)]
[New Thread 815f01c00 (LWP 101348)]
[New Thread 815f2b400 (LWP 101349)]
[New Thread 815f2b800 (LWP 101350)]

Program received signal SIGBUS, Bus error.
[Switching to Thread 815c07400 (LWP 101407)]
0x0000000806769b50 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
(gdb) c
Continuing.
[Inferior 1 (process 4379) exited normally]
That is, it just starts for some seconds, and that exits not even showing anything.

Tried with gcc48 and gcc49, with base clang it couldn't compile at all:
clang++: error: unsupported argument '--version' to option 'Xassembler'
compiler_version.py failed to execute: clang++ -Xassembler --version -x assembler -c /dev/null
also with clang35.

And yes, I can't compile chromium with TEST option ON.
Comment 1 gja822 2014-10-26 19:16:20 UTC
Still the same with 38.0.2125.104_1
Comment 2 Rene Ladan freebsd_committer freebsd_triage 2014-10-26 21:26:07 UTC
The TEST option is currently broken. Fixing it seems harder than it should (modifying the build infrastructure a bit).

Clang is the version shipped with FreeBSD (3.3) ? That works fine here on 10.0-amd64. Also, clang should work fine (but appearantly it doesn't) since upstream uses that.
Comment 3 gja822 2014-10-27 04:27:12 UTC
On my 9.3 it doesn't work, It compiles, but doesn't start with gcc48, gcc49, clang35 from ports.

Base clang on latest 9.3 states that it is "3.4.1". And it doesn't work. Unlike other my compilers, base clang doesn't do even the configure step:

clang++: error: unsupported argument '--version' to option 'Xassembler'
compiler_version.py failed to execute: clang++ -Xassembler --version -x assembler -c /dev/null
Command 'clang++ -Xassembler --version -x assembler -c /dev/null' returned non-zero exit status 1
Exception: Failed to extract compiler version for args: ['target', 'assembler']
Traceback (most recent call last):
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 484, in CallLoadTargetBuildFile
    includes, depth, check, False)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 399, in LoadTargetBuildFile
    build_file_data, PHASE_EARLY, variables, build_file_path)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1193, in ProcessVariablesAndConditionsInDict
    variables, build_file, 'variables')
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1245, in ProcessVariablesAndConditionsInDict
    ProcessConditionsInDict(the_dict, phase, variables, build_file)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1124, in ProcessConditionsInDict
    variables, build_file)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1245, in ProcessVariablesAndConditionsInDict
    ProcessConditionsInDict(the_dict, phase, variables, build_file)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1124, in ProcessConditionsInDict
    variables, build_file)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 1200, in ProcessVariablesAndConditionsInDict
    expanded = ExpandVariables(value, phase, variables, build_file)
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/tools/gyp/pylib/gyp/input.py", line 897, in ExpandVariables
    replacement = str(py_module.DoMain(parsed_contents[1:])).rstrip()
  File "/usr/ports/www/chromium/work/chromium-38.0.2125.104/native_client/build/compiler_version.py", line 122, in DoMain
    raise Exception("Failed to extract compiler version for args: %s" % args)
Exception: Failed to extract compiler version for args: ['target', 'assembler']

*** [do-configure] Error code 1

Most of other ports I've compiled with gcc48.
Comment 4 mzs_47 2015-08-08 00:45:05 UTC
This happens on one of the machine, on which an addon did not install properly, after which I have removed and reinstalled www/chromium with pkg multiple times, and removed ~/.config/chrome, ~/.cache/chrome, ~/.chrome.core to make it start.

It worked a few time times after this, but later it stopped connecting to internet, It does not start anymore, I see disk activity when I run the command and it just stops after that.

uname -a
FreeBSD freebsd-dellE6430 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue Jul 28 12:04:19 UTC 2015     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

pkg info chromium
chromium-44.0.2403.125
Name           : chromium
Version        : 44.0.2403.125
Installed on   : Tue Aug  4 21:48:46 IST 2015
Origin         : www/chromium
Architecture   : freebsd:10:x86:64
Prefix         : /usr/local
Categories     : www
Licenses       : MPL and LGPL21 and BSD3CLAUSE
Maintainer     : chromium@FreeBSD.org
WWW            : http://www.chromium.org/Home
Comment        : Google web browser based on WebKit
Options        :
	CODECS         : on
	DEBUG          : off
	GCONF          : on
	KERBEROS       : on
	PULSEAUDIO     : off
	TEST           : off
Comment 5 Walter Schwarzenfeld 2018-01-12 15:07:06 UTC
We have version 61.0.3163.100. I think this is overcome by events.