chromium-browser native build issues

piojo · 2009-08-20 15:17:18

Hello! I made a not-yet-working PKGBUILD for chromium-browser, and this page is a place to discuss its issues.

Let me mention why this PKGBUILD is different: it seems all the others download binary packages from other places and modify them so they work on Arch. That seems unnecessary for an open source program, and fragile. On to the issues:

First, chrome doesn't build--it fails to link the "chrome" executable. It looks to me like it's not being linked properly to webkit.

There is no "make install" target, so the relevant files must be placed in $pkgdir by hand.

Because of the above issues, I can't find where exactly the executables and resources need to go to find each other.

The code is a little different for 32-bit and 64-bit installations. Specifically, Google says that to compile this on 64 bit, we need to pull newest unstable version of v8, the javascript library. It's possible that the build currently does work for 32-bit users, but I suspect not.

I think the first course of action is investigating the linking problem. The symbol that isn't found is "findEntity(char const*, unsigned int)"

Last edited by piojo (2009-08-20 15:20:45)

piojo · 2009-08-20 15:19:04

Another issue is that depot_tools-svn (a dependency) is broken. I posted a fixed PKGBUILD on the aur page, but the md5sums will break every time someone makes a commit to depot_tools. I don't know how to fix this--I think makepkg should allow missing md5sums for this reason.

wonder · 2009-08-20 15:30:21

piojo did you look at those patches from fedora that i give you? there you can look at the spec to see what you need to copy in pkgdir.

link: http://spot.fedorapeople.org/chromium/

Last edited by wonder (2009-08-20 15:31:58)

piojo · 2009-08-20 16:30:44

wonder wrote:

piojo did you look at those patches from fedora that i give you? there you can look at the spec to see what you need to copy in pkgdir.
link: http://spot.fedorapeople.org/chromium/

Yes, thank you. That .spec will be really useful. As for the patches, I'll see whether they're necessary after I get chromium to finish building. (The patches won't help with the particular build issue I'm having, because they involve compiling against locally installed libraries, which seem to be found fine, so far.)

flamelab · 2009-08-20 19:11:36

I had this annoying message: Argument list too long

but I didn't really understand how to solve this problem hmm

piojo · 2009-08-20 19:57:27

flamelab wrote:

I had this annoying message: Argument list too long

Solve it by building in a shorter directory. "/tmp/chrome" might be short enough, but "/tmp/c" definitely works. If you don't have enough space in /tmp, bind-mount your chrome package directory to /tmp/c:

mkdir /tmp/c
sudo mount --bind /home/flamelab/packages/chrome-browser/ /tmp/c/
cd /tmp/c; makepkg

This alone won't be enough to make the compilation finish, though. There's a link problem toward the end, and I'm poking at that, trying to fix it...

lilsirecho · 2009-08-20 20:51:29

Perhaps ....

mount -o remount,size=3G /

This will give you max tmpfs size and allow swap if needed.

Max size isn't necessarily 3G but whatever your ram size is will be its useful range.

flamelab · 2009-08-20 21:33:42

piojo wrote:

flamelab wrote:
I had this annoying message: Argument list too long
Solve it by building in a shorter directory. "/tmp/chrome" might be short enough, but "/tmp/c" definitely works. If you don't have enough space in /tmp, bind-mount your chrome package directory to /tmp/c:
mkdir /tmp/c
sudo mount --bind /home/flamelab/packages/chrome-browser/ /tmp/c/
cd /tmp/c; makepkg
This alone won't be enough to make the compilation finish, though. There's a link problem toward the end, and I'm poking at that, trying to fix it...

Thank you, I'll try it.

But...

Isn't that error very ...stupid ? Is it a bash error ? A "make" error ?

piojo · 2009-08-20 22:36:22

flamelab wrote:

Isn't that error very ...stupid ? Is it a bash error ? A "make" error ?

It's more of a Linux error. There's a maximum argument length that the "exec" functions can be called with. This seems to be defined in /usr/src/linux-2.6.30-ARCH/include/linux/limits.h (my source is http://www.in-ulm.de/~mascheck/various/argmax/ , but I checked it myself). It's funny, because I remember discussion on the linux kernel mailing list about removing this limit entirely, and having the arg length be limited by available memory.

Note that this space limit also applies to environment variables (as limits.h seems to imply), so if need to save even more space, you can try "env - PATH=$PATH USER=$USER HOME=$HOME make -r chrome" instead of just "make -r chrome" (http://www.linuxquestions.org/questions/linux-software-2/execvp-binsh-argument-list-too-long-compilation-error-723076/ ). I didn't need to do that, though.

When you get down to it, though, I think it's really an error in chromium's build system. This just shouldn't happen, because practically every linux script writer knows that you can't have infinitely long arguments.

Last edited by piojo (2009-08-20 23:07:43)

piojo · 2009-08-20 23:29:06

Also, I found the "final" error being discussed here:

http://groups.google.com/group/chromium … e42661344f

If everything else goes right, this linker error will still stop the chrome executable from being produced on arch-linux. I guess this is why every other packager just grabbed a binary package from another distro. I'll be watching this thread and waiting for a solution. I can't figure out why the link fails, because it really looks like it should succeed, from the debugging I've done.

adamruss · 2009-08-21 00:33:36

this works for me on 64:

PKGBUILD to make the 64-bit version (NATIVE!) work. Note that's it's
JUST the 64-bit version.

# Contributor: Christer Edwards <christer@zelut.org>
# PKGBUILD FAQ: http://blog.zelut.org/chromium-browser-faq-arch/
pkgname=chromium-browser
pkgver=4.0.203.0~svn20090818r23670
pkgrel=1
pkgdesc="Chromium is an open-source browser project that aims to
build a safer, faster, and more stable way for all Internet users to
experience the web."
url="http://code.google.com/chromium/"
if [ "${CARCH}" = 'x86_64' ]; then
depends=('atk' 'gtk2' 'nss' 'gconf' 'cairo' 'freetype2' 'dbus-glib'
'libjpeg6')
elif [ "${CARCH}" = 'i686' ]; then
depends=('atk' 'gtk2' 'nss' 'gconf' 'cairo' 'freetype2' 'dbus-glib')
fi
arch=('i686' 'x86_64')
license=('BSD')
conflicts=('chromium-snapshot')
source=(http://ppa.launchpad.net/chromium-daily/ppa/ubuntu/pool/main/c/chromium-browser/chromium-browser_${pkgver}-0ubuntu1~ucd1_amd64.deb)
md5sums=('9854278fd5211ec757cfaac2dc04af8f')

build() {
cd $srcdir

bsdtar xf "chromium-browser_${pkgver}-0ubuntu1~ucd1_amd64.deb" ||
return 1
bsdtar xf data.tar.gz -C $pkgdir || return 1

}

piojo · 2009-08-21 02:41:34

adamruss wrote:

this works for me on 64:
...

I see--thanks. That's not a source package, though, that's installing a .deb from ubuntu . Anyway, I appreciate it, but I'm not ready to give up on compiling from source, yet. (This problem may be way out of my league, but I feel stubborn...)

Thanks, anyway.

PixelSmack · 2009-08-23 19:18:28

piojo wrote:

Also, I found the "final" error being discussed here:
http://groups.google.com/group/chromium … e42661344f
If everything else goes right, this linker error will still stop the chrome executable from being produced on arch-linux. I guess this is why every other packager just grabbed a binary package from another distro. I'll be watching this thread and waiting for a solution. I can't figure out why the link fails, because it really looks like it should succeed, from the debugging I've done.

From all the investigation i have done the problem seems to be something to do with gperf, i am wondering now if this is a compiler flag we are missing although i've not really been sure where to start. I have tried to build nightlys of webkit as well however they are linked against the betas of libsoup and i don't really have anywhere to test these on. If anyone is feeling brave that may be a good place to explore this problem.

wonder · 2009-08-24 19:52:59

@piojo here is a build from gentoo: http://forums.gentoo.org/viewtopic-p-59 … ml#5942129

Gen2ly · 2009-08-25 05:16:08

I also noticed that chromium-browser-svn in AUR now compiles x86_64 (or is supposed to, haven't tried yet).

piojo · 2009-08-26 16:40:24

Apparently, the package compiles if BUILDTYPE is set to "Release". That result isn't very satisfying... I don't really know any more than I did before. But the package now works, please test it if you are interested. http://aur.archlinux.org/packages.php?ID=29440

You will need 5GB of disk space and (probably) a few hours to build it (sorry).

wonder · 2009-08-26 17:00:05

thanks piojo

Gen2ly · 2009-08-26 17:34:01

Yeah, thanks. I'll get to trying this later.

wonder · 2009-08-26 17:48:15

i see on fedora spec that there is chrome-sanbox but we are not having this. i think is a good feature that needs to be added. that sandbox is on http://code.google.com/p/chromium/wiki/LinuxPackaging too. maybe you forgot about it.

lilsirecho · 2009-08-26 18:16:51

Used your aur URL to download the tarball.

When running the PKGBUILD, depot_tools-svn is missing. Aborted.

Observed the notes in the aur such that depot_tools is correct and should be included in the PKGBUILD. What is the situation now regarding this item?

lilsirecho · 2009-08-27 04:10:55

Determined that I needed to use the aur for several PKGBUILDS before being able to start the Chromium-browser-svn PKGBUILD.

Was able to install the needed packages, and began the PKGBUILD for the browser at ~2pm.

At ~7;30 pm, the MAKE began and at ~845pm the build aborted with the error :

cp extensions :no such file or directory

You could call this elephantus gigantus! (885MB in the download).

Where did extensions go?

What to do?

timefairy · 2010-04-21 02:55:37

Edited: oops... I changed to yaourt-git, and it works fine :-)
-----
Don't know why, but whenever I use yaourt for this "Chromium-browser-svn" (http://aur.archlinux.org/packages.php?ID=29440), after "Finished making: chromium-browser-svn" message, will show this error:

loading package data...
error: './chromium-browser-svn-2010-38-x86_64.pkg.tar.xz': cannot open package file
==> WARNING: Your package is saved in /tmp/yaourt-tmp-mark/chromium-browser-svn-2010-38-x86_64.pkg.tar.xz
cp: cannot stat `./chromium-browser-svn-2010-38-x86_64.pkg.tar.xz': No such file or directory
==> WARNING: Unable to copy chromium-browser-svn-38-x86_64.pkg.tar.xz to /tmp/yaourt-tmp-mark/ directory

And I couldn't find any chromium-*-pkg.* in the /tmp/ directory...

Any way, run the PKGBUILD by "makepkg" works well. Thank you :-)

Last edited by timefairy (2010-04-21 05:19:05)

flamelab · 2010-04-21 03:41:30

You should report this to the yaourt guys on archlinuxfr

tomk · 2010-04-21 06:05:49

timefairy - this is an old thread. See here for further details.

Apart from that, your issue was with yaourt, not chromium, so a new thread would have been more appropriate anyway.

Closed.

Arch Linux

#1 2009-08-20 15:17:18

chromium-browser native build issues

#2 2009-08-20 15:19:04

Re: chromium-browser native build issues

#3 2009-08-20 15:30:21

Re: chromium-browser native build issues

#4 2009-08-20 16:30:44

Re: chromium-browser native build issues

#5 2009-08-20 19:11:36

Re: chromium-browser native build issues

#6 2009-08-20 19:57:27

Re: chromium-browser native build issues

#7 2009-08-20 20:51:29

Re: chromium-browser native build issues

#8 2009-08-20 21:33:42

Re: chromium-browser native build issues

#9 2009-08-20 22:36:22

Re: chromium-browser native build issues

#10 2009-08-20 23:29:06

Re: chromium-browser native build issues

#11 2009-08-21 00:33:36

Re: chromium-browser native build issues

#12 2009-08-21 02:41:34

Re: chromium-browser native build issues

#13 2009-08-23 19:18:28

Re: chromium-browser native build issues

#14 2009-08-24 19:52:59

Re: chromium-browser native build issues

#15 2009-08-25 05:16:08

Re: chromium-browser native build issues

#16 2009-08-26 16:40:24

Re: chromium-browser native build issues

#17 2009-08-26 17:00:05

Re: chromium-browser native build issues

#18 2009-08-26 17:34:01

Re: chromium-browser native build issues

#19 2009-08-26 17:48:15

Re: chromium-browser native build issues

#20 2009-08-26 18:16:51

Re: chromium-browser native build issues

#21 2009-08-27 04:10:55

Re: chromium-browser native build issues

#22 2010-04-21 02:55:37

Re: chromium-browser native build issues

#23 2010-04-21 03:41:30

Re: chromium-browser native build issues

#24 2010-04-21 06:05:49

Re: chromium-browser native build issues

Board footer