"unterminated quoted string" when building on Linux x86

[Eric Millin]

I've had a very difficult time building Chromedriver for x86 Linux. I'm using a machine running Trusty i386. Currently when I try to build it fails almost immediately, reporting the file (any one of several) failed to compile due to "Syntax Error: Unterminated quoted string." I tried the Chrome target and see the same thing. I have set the target_arch to ia32 and afaik followed the instructions to the letter. Any suggestions on what I might try?

[Dirk Pranke]

My first guess is that you have a bad #define somewhere.

Maybe file a bug and post a sample command and the error, along with any GYP_DEFINES you might have set?

-- Dirk

On Sun, Apr 5, 2015 at 5:45 PM, Eric Millin <etmi...@gmail.com> wrote:

I've had a very difficult time building Chromedriver for x86 Linux. I'm using a machine running Trusty i386. Currently when I try to build it fails almost immediately, reporting the file (any one of several) failed to compile due to "Syntax Error: Unterminated quoted string." I tried the Chrome target and see the same thing. I have set the target_arch to ia32 and afaik followed the instructions to the letter. Any suggestions on what I might try?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev

[Jakob Kummerow]

Last time I heard about this error message, it was due to building with the bundled clang, which is a 64-bit binary, on a 32-bit system. To even have a chance to get it to build, you'll have to fall back to your system's GCC, by using GYP_DEFINES="clang=0". 

However, AFAIK building Chromium on 32-bit hosts is generally unsupported, and you might run into further problems (such as the linker having insufficient address space; using the component build may or may not work around that). Using a 64-bit machine is strongly recommended.

[Eric Millin]

AFAIK building Chromium on 32-bit hosts is generally unsupported

I'm very confused by this. According to the Chromium documentation:

OBSOLETE: Building 32-bit Chromium on 64-bit Linux is no longer officially supported. The "32-bit compatibility libs" instructions probably won't work. The chroot instructions are your best bet, but it is not actively tested or maintained.

What exactly is the recommend build environment?  Is it using Chroot on x64?

[Eric Millin]

I tried again on a Vagrant Precise32 instance.  Here are the steps I followed, more or less: https://gist.github.com/0x1mason/5c9dd03c22fd765fec5e

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

--

Eric Millin

Software Engineer, Ecosystems

Twitter: @etmillin

GitHub: @0x1mason

Sauce Labs | Sauce blog

[Jakob Kummerow]

On Tue, Apr 7, 2015 at 4:52 PM, Eric Millin <er...@saucelabs.com> wrote:

I tried again on a Vagrant Precise32 instance.  Here are the steps I followed, more or less: https://gist.github.com/0x1mason/5c9dd03c22fd765fec5e

As I said before, at the very least you'll need GYP_DEFINES="clang=0". If the linker runs out of memory, try GYP_DEFINES="clang=0 component=shared_library".

On Tue, Apr 7, 2015 at 10:44 AM, Eric Millin <er...@saucelabs.com> wrote:

AFAIK building Chromium on 32-bit hosts is generally unsupported

I'm very confused by this. According to the Chromium documentation:

OBSOLETE: Building 32-bit Chromium on 64-bit Linux is no longer officially supported. The "32-bit compatibility libs" instructions probably won't work. The chroot instructions are your best bet, but it is not actively tested or maintained.

What exactly is the recommend build environment?  Is it using Chroot on x64?

It's what I do. But it won't quite work out of the box, you'll have to mess with the package manager inside the chroot a bit (just follow the error messages).

I don't think many people are regularly building 32-bit Chromium at all.

[Torne (Richard Coles)]

Yeah, building in a 32-bit chroot is the right way to do it. The scripts that attempt to automate setting up the chroot for you are what is not being actively tested or maintained. The actual process of building chrome in a 32-bit chroot is fine; it's what all the 32-bit buildbots do.

[Eric Millin]

Thanks for the help.  You got me pointed in the right direction.  I finally got it building with `export GYP_DEFINES="clang=0 target_arch=ia32 component=shared_library"` and some library finagling.