How to get the old version source?

662 views
Skip to first unread message

M.Yamada

unread,
Dec 4, 2013, 8:36:07 PM12/4/13
to chromi...@chromium.org
I would like to correct and try Chromium of an old version( version 19). 
So I want to get the source of version 19 of chromium, but can not get well.

My build environment is ubuntu 23.04 LTS 

I tried as follows.
 
  $ cd  /home/ubuntu
  $ export PATH="$PATH":/home/ubuntu/depot_tools

  $ mkdir chromium19
  $ cd chromium19
  $ gclient sync

    Error: Command svn checkout http://jsoncpp.svn.sourceforge.net/svnroot/jsoncpp/trunk/jsoncpp/src/lib_json@248 /home/ubuntu/chromium19/src/third_party/jsoncpp/source/src/lib_json --revision 248 --non-interactive --ignore-externals returned non-zero exit status 1 in /home/ubuntu/chromium19


Someone, please tell me how to get the old source.

Thanks

Lei Zhang

unread,
Dec 4, 2013, 10:20:21 PM12/4/13
to 山田雅昭, Chromium-dev
If you search this list for jsoncpp, you'll find several emails
regarding this. IIRC, SourceForge changed the svn URL for projects
they host, so an old version like M19 still have the old path. Those
off course worked at the time, but not anymore. Since releases older
than the current stable release are not supported, nobody will bother
to go back and change the URLs.
> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev

Luis de Bethencourt

unread,
Dec 4, 2013, 10:24:27 PM12/4/13
to the...@chromium.org, 山田雅昭, Chromium-dev
Most distributions keep a copy of the source package used to build the package they release.
Since you mention Ubuntu, here is a list of the Chromium packages for that Distribution.


You can get a tarball that will build from there. Source packages are listed as orig.tar.xz in the right column of each packages page.

I hope this helps.


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

M.Yamada

unread,
Dec 5, 2013, 3:24:00 AM12/5/13
to chromi...@chromium.org, 山田雅昭
Hi, Lei Zhang

Oh, sources of chromium are separately managed by a lot of URL. 
And, it was changed.
I did not know.

I was not able to find the URL of the new jsoncpp.

I tried to skip to get the jsonspp.
And then I copy form jsonspp current version.

So, I  will try to build test.

Thank you for the advice.


M.Yamada

2013年12月5日木曜日 12時20分21秒 UTC+9 Lei Zhang:

M.Yamada

unread,
Dec 5, 2013, 3:39:09 AM12/5/13
to chromi...@chromium.org, the...@chromium.org, 山田雅昭, lu...@debethencourt.com
Hi, Luis de Bethencourt

I did not think that there is way to get from the source of the ubuntu package
It's great!

I will try to get.

Thank you for your idea.

M.Yamada


2013年12月5日木曜日 12時24分27秒 UTC+9 Luis de Bethencourt:

Primiano Tucci

unread,
Dec 5, 2013, 4:51:59 AM12/5/13
to yama...@gmail.com, Chromium-dev, the...@chromium.org, lu...@debethencourt.com
If the problem you are encountering is related only to gclient (as it looks from your output) and you're interested just in getting a snapshot of chrome m19 code, you can try the following:
- Get the svn revision corresponding to 19.0.1060.0 from omahaproxy --> r124888
- Look for the corresponding tarball in the Google storage archives: http://chromium-browser-source.commondatastorage.googleapis.com/chromium.r124888.tgz

As long as you just need the code the tarball should be fine.

Also note that building older versions of chrome in recent Ubuntu releases can be pretty tricky, as many of the system dependencies have gone or have been upgraded.
I can't tell exactly how to deal with m19, but some months ago I did a build of m12 and it was a bit tricky.
Some random tips which might eventually help:
  • If you encounter weird compiler-related errors try to go back to an older version of GCC. For Chrome m12 I had to:
    export CXX=g++-4.4
    export CC=gcc-4.4
    and then re-run gyp-chromium
  • If you are used to build with ninja, remember that it might not have been there back in times (definitely it wasn't for m12). In that case you'll need to fall back to the good bad old makefile:
    export GYP_GENERATORS=
    export GYP_DEFINES=
    (in general make sure you start in a clean shell environment)
  • You might still need to hack a bit with the gyp files to upgrade/remove dependencies.
Cheers,
Primiano



Luis de Bethencourt

unread,
Dec 5, 2013, 8:00:20 PM12/5/13
to M.Yamada, Chromium-dev, the...@chromium.org
My pleasure :)

M.Yamada

unread,
Dec 6, 2013, 2:55:35 AM12/6/13
to chromi...@chromium.org, yama...@gmail.com, the...@chromium.org, lu...@debethencourt.com
Hi, Primiano Tucci 

I was able to get the source of purpose very easily , thanks to your advice. 
However, as your advice, it becomes a lot of build error.

I will fight to succeed the build.
Thank you for your advice.

  M.Yamada




2013年12月5日木曜日 18時51分59秒 UTC+9 Primiano Tucci:
Reply all
Reply to author
Forward
0 new messages