From owner-freebsd-chromium@FreeBSD.ORG Wed Jan 14 06:07:52 2015 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 49F9DFA for ; Wed, 14 Jan 2015 06:07:52 +0000 (UTC) Received: from mail-wi0-x241.google.com (mail-wi0-x241.google.com [IPv6:2a00:1450:400c:c05::241]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4D7EBA9 for ; Wed, 14 Jan 2015 06:07:51 +0000 (UTC) Received: by mail-wi0-f193.google.com with SMTP id bs8so2373522wib.0 for ; Tue, 13 Jan 2015 22:07:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UxbTfSwY/s7OMIk6B0rL17SxGgVfQlkjmyygqEqiyjs=; b=KZqGkBVmzcxRO6UTwe01uUqYXzi+Tvrh9KXCL0rkMvjwT1d/LvtzDM/IYV18enzGnH Hc2cenZb5RZ/WJAvIfiW5KgC/4LdVtpOUg2Lv/dJ/UZqslYTIHdrwTgQ1yWPA94gNJ42 +XgEmk92VOXTbt3ml2hPngP7ysDsyey3s+HyrxJvK8olJg/GFc31zNOdkzc/q8eAJpB0 t1lQo/94YI3B1MdweDJ5LEahal5dmR3bMZmZEiir+vefbuWRJmUBKkkpBTNQoG6jNqOA VCGem9eV58xOF+JvoGoootJUundmdRtmENIXHIqlZacTtemOLLTr9t+6pXL55CgV9uvU vTlQ== MIME-Version: 1.0 X-Received: by 10.180.88.33 with SMTP id bd1mr12871762wib.10.1421215670303; Tue, 13 Jan 2015 22:07:50 -0800 (PST) Received: by 10.216.176.71 with HTTP; Tue, 13 Jan 2015 22:07:50 -0800 (PST) Date: Wed, 14 Jan 2015 10:07:50 +0400 Message-ID: Subject: patch to allow building chromium without Kerberos From: Igor R To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 06:07:52 -0000 Hello! I have built my FreeBSD system with WITHOUT_KERBEROS=yes in /etc/src.conf (there are also more WITHOUT_* lines here). But chromium port builds with GSSAPI by default. So I have made simple patch, which allows to build chromium without gssapi using settings from /etc/src.conf: ===== diff --git a/www/chromium/Makefile b/www/chromium/Makefile index 073f6a6..064f0a5 100644 --- a/www/chromium/Makefile +++ b/www/chromium/Makefile @@ -1,6 +1,8 @@ # Created by: Florent Thoumie # $FreeBSD$ +.include "/etc/src.conf" + #TODO bz@ : if you do undestand the gyp stuff, third_party/widevine/cdm/widevine_cdm.gyp talks about it (plz install libwidevinecdm.so) PORTNAME= chromium PORTVERSION= 39.0.2171.95 @@ -206,6 +208,10 @@ EXTRA_PATCHES+= ${FILESDIR}/extra-patch-clang CONFIGURE_ENV+= AR=/usr/bin/ar .endif +.if ${WITHOUT_KERBEROS} == yes +GYP_DEFINES+= use_kerberos=0 +.endif + # according to portlint the below is passed via bsd.port.mk, # but 'make -V CONFIGURE_ENV' does not show it: CONFIGURE_ENV+= CFLAGS="${CFLAGS}" \ ===== From owner-freebsd-chromium@FreeBSD.ORG Wed Jan 14 15:06:23 2015 Return-Path: Delivered-To: freebsd-chromium@FreebSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2206D57C for ; Wed, 14 Jan 2015 15:06:23 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D305CD6A for ; Wed, 14 Jan 2015 15:06:19 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YBPWN-0000TS-Qg for freebsd-chromium@FreebSD.org; Wed, 14 Jan 2015 16:06:11 +0100 Received: from firewall.andxor.it ([78.134.40.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Jan 2015 16:06:11 +0100 Received: from lapo by firewall.andxor.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Jan 2015 16:06:11 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-chromium@FreebSD.org From: Lapo Luchini Subject: Latest Chromium with NPAPI and Hangout support Date: Wed, 14 Jan 2015 16:05:59 +0100 Lines: 11 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: firewall.andxor.it User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 OpenPGP: id=CBDA71F0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 15:06:23 -0000 ...is release 35.0.1916.153 and just in case anybody else is interested in using it, I'm keeping a copy of the Port working here: https://github.com/lapo-luchini/FreeBSD-Ports/tree/master/www/chromium I don't really understand the choice to remove NPAPI when Java still hasn't any alternative to it; plugins may be "bad", but sometimes they're just a necessity (Flash too, unfortunately). -- Lapo Luchini - http://lapo.it/ From owner-freebsd-chromium@FreeBSD.ORG Thu Jan 15 11:05:49 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE99651B for ; Thu, 15 Jan 2015 11:05:49 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 95CBDF4D for ; Thu, 15 Jan 2015 11:05:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FB5n3g071852 for ; Thu, 15 Jan 2015 11:05:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 196754] www/chromium 39.0.2171.95_3 segfaults during login with security key Date: Thu, 15 Jan 2015 11:05:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rod@lpho.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 11:05:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196754 Bug ID: 196754 Summary: www/chromium 39.0.2171.95_3 segfaults during login with security key Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: rod@lpho.de Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Hello, I have www/chromium 39.0.2171.95_3 installed from the binary package (tried compiling it myself, but the result was the same) and it segfaults when I try to login using an account which uses a security key (Yubico Nano). While I didn't expect support for the Yubico device to work right away, the segfault was a surprise. The problem occurs even when the security key is not inserted. Logging in with an account which does not use a security key works fine. I'm rebuilding chrome now with debug option, so the core file makes more sense. >From truss: stat("/usr/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/local/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/local/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file or directory' Segmentation fault (core dumped) write(2,"Segmentation fault (core dumped)"...,33) = 33 (0x21) read(10,0x623330,1024) = 0 (0x0) process exit, rval = 139 (I've already manually build libc.cat and it's independent from this issue). >From chrome_debug.log: [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114814:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue Thanks --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Thu Jan 15 11:05:49 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9972E51A for ; Thu, 15 Jan 2015 11:05:49 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6AF5CF4C for ; Thu, 15 Jan 2015 11:05:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FB5nJc071844 for ; Thu, 15 Jan 2015 11:05:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 196754] www/chromium 39.0.2171.95_3 segfaults during login with security key Date: Thu, 15 Jan 2015 11:05:49 +0000 X-Bugzilla-Type: request Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 11:05:49 -0000 Rodolpho Eckhardt has reassigned Bugzilla Automation 's request for maintainer-feedback to chromium@FreeBSD.org: Bug 196754: www/chromium 39.0.2171.95_3 segfaults during login with security key https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196754 --- Description --- Hello, I have www/chromium 39.0.2171.95_3 installed from the binary package (tried compiling it myself, but the result was the same) and it segfaults when I t= ry to login using an account which uses a security key (Yubico Nano). While I didn't expect support for the Yubico device to work right away, the segfault was a surprise. The problem occurs even when the security key is not inserted. Logging in with an account which does not use a security key works fine. I'm rebuilding chrome now with debug option, so the core file makes more se= nse. >From truss: stat("/usr/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No such f= ile or directory' stat("/usr/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file = or directory' stat("/usr/local/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No = such file or directory' stat("/usr/local/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file or directory' Segmentation fault (core dumped) write(2,"Segmentation fault (core dumped)"...,33) =3D 33 (0x21) read(10,0x623330,1024) =3D 0 (0x0) process exit, rval =3D 139 (I've already manually build libc.cat and it's independent from this issue). >From chrome_debug.log: [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114814:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue Thanks --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org= From owner-freebsd-chromium@FreeBSD.ORG Thu Jan 15 17:14:50 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 554FCB9C for ; Thu, 15 Jan 2015 17:14:50 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3BCAA123 for ; Thu, 15 Jan 2015 17:14:50 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FHEogF090108 for ; Thu, 15 Jan 2015 17:14:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 196754] www/chromium 39.0.2171.95_3 segfaults during login with security key Date: Thu, 15 Jan 2015 17:14:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rod@lpho.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 17:14:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196754 --- Comment #2 from Rodolpho Eckhardt --- Unfortunately, I cannot get www/chromium to work with the debug option enabled. I found some previous posts which refer to this issue, but no open bug, so I'll open a new one for that issue. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Thu Jan 15 17:18:39 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF08CE16 for ; Thu, 15 Jan 2015 17:18:39 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB150159 for ; Thu, 15 Jan 2015 17:18:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FHIdGD093030 for ; Thu, 15 Jan 2015 17:18:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 196770] www/chromium does not run if built with DEBUG option Date: Thu, 15 Jan 2015 17:18:39 +0000 X-Bugzilla-Type: request Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 17:18:39 -0000 Rodolpho Eckhardt has reassigned Bugzilla Automation 's request for maintainer-feedback to chromium@FreeBSD.org: Bug 196770: www/chromium does not run if built with DEBUG option https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196770 --- Description --- If www/chromium is built with the DEBUG option, the result is an executable which does not work: $ chrome /usr/local/bin/chrome: /usr/local/share/chromium/chrome: Exec format error $ file /usr/local/share/chromium/chrome /usr/local/share/chromium/chrome: data $ hd /usr/local/share/chromium/chrome 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * I found some previous references to this issue, but the solution was just to avoid building with the debug option: http://freebsd.1045724.n5.nabble.com/chromium-37-up-for-testing-and-polishing-t d5941131i20.html#a5943220 http://permalink.gmane.org/gmane.os.freebsd.devel.ports/120227 Thanks! --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org From owner-freebsd-chromium@FreeBSD.ORG Thu Jan 15 17:18:40 2015 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0AC14E17 for ; Thu, 15 Jan 2015 17:18:40 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E612215A for ; Thu, 15 Jan 2015 17:18:39 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FHIdmN093033 for ; Thu, 15 Jan 2015 17:18:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 196770] www/chromium does not run if built with DEBUG option Date: Thu, 15 Jan 2015 17:18:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rod@lpho.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 17:18:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196770 Bug ID: 196770 Summary: www/chromium does not run if built with DEBUG option Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: rod@lpho.de Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) If www/chromium is built with the DEBUG option, the result is an executable which does not work: $ chrome /usr/local/bin/chrome: /usr/local/share/chromium/chrome: Exec format error $ file /usr/local/share/chromium/chrome /usr/local/share/chromium/chrome: data $ hd /usr/local/share/chromium/chrome 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * I found some previous references to this issue, but the solution was just to avoid building with the debug option: http://freebsd.1045724.n5.nabble.com/chromium-37-up-for-testing-and-polishing-td5941131i20.html#a5943220 http://permalink.gmane.org/gmane.os.freebsd.devel.ports/120227 Thanks! --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.