Can you find out what revision the build broke at?

The version is Chromium 6.0.472.0(52986).
It is the latest code in July,20th.

Are you saying r52986 was the last revision you successfully built? The first revision that failed for you? The only revision you tried?

r52986 is the version I tried yesterday and failed both with CodeSourcery and gold.
I used the CodeSourcery toolchain several weeks ago, it always successed.

If I set arm_thumb=0, then linked with CodeSorucery toolchain successed with the latest Chromium code.

Anyway you can verify the latest code with gold linker. 

Then please see comment 1. The code builds fine with our toolchain:
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Arm

If you want to figure out why it's broken with your toolchain, you have to do some of the work and tell us when exactly it broken.

variable:
{
  'variables': {
    'target_arch': 'arm',
    'sysroot': '/home/b15608/Chromium/rootfs',
    'disable_nacl': 1,  # NaCL does not build for ARM.
    'linux_use_tcmalloc': 0, # tcmalloc does not build for ARM.
    'toolkit_views': 1,
    'armv7': 1, # Optional, for targeting ARMv7.
    'arm_thumb': 0, # Optional, for targetting thumb.  Combine with armv7 to target thumb2.
    'arm_neon':1,
    'remove_webcore_debug_symbols': 1,
    'enable_svg':0,
  }

Toolchain:
export CROSSTOOL=/home/b15608/Chromium/arm-2009q3/bin/arm-none-linux-gnueabi
export CXX="$CROSSTOOL-g++ -B /home/b15608/Chromium"
export CC="$CROSSTOOL-gcc  -B /home/b15608/Chromium"
export AR=$CROSSTOOL-ar
export AS=$CROSSTOOL-as
export RANLIB=$CROSSTOOL-ranlib
export LD=/home/b15608/Chromium/ld

(gold/ld-new is soft linked as ld in /home/b15608/Chromium)

Error prompt:
 /home/b15608/Chromium/arm-2009q3/bin/arm-none-linux-gnueabi-g++ -B /home/b15608/Chromium  -Werror -pthread -fno-exceptions -Wall -Wno-unused-parameter -Wno-missing-field-initializers -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -fno-strict-aliasing -D_REENTRANT -pthread -I/home/b15608/Chromium/rootfs/usr/include/gtk-2.0 -I/home/b15608/Chromium/rootfs/usr/lib/gtk-2.0/include -I/home/b15608/Chromium/rootfs/usr/include/atk-1.0 -I/home/b15608/Chromium/rootfs/usr/include/cairo -I/home/b15608/Chromium/rootfs/usr/include/pango-1.0 -I/home/b15608/Chromium/rootfs/usr/include/pixman-1 -I/home/b15608/Chromium/rootfs/usr/include/freetype2 -I/home/b15608/Chromium/rootfs/usr/include/directfb -I/home/b15608/Chromium/rootfs/usr/include/libpng12 -I/home/b15608/Chromium/rootfs/usr/include/glib-2.0 -I/home/b15608/Chromium/rootfs/usr/lib/glib-2.0/include -march=armv7-a -mtune=cortex-a8 -mfloat-abi=softfp -mfpu=neon --sysroot=/home/b15608/Chromium/rootfs -O2 -fno-ident -fdata-sections -ffunction-sections -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -Wno-abi '-DNO_TCMALLOC' '-DNO_HEAPCHECKER' '-DDISABLE_NACL' '-DCHROMIUM_BUILD' '-DTOOLKIT_VIEWS=1' '-DENABLE_REMOTING=1' '-DENABLE_GPU=1' '-DGL_GLEXT_PROTOTYPES' '-DU_STATIC_IMPLEMENTATION' '-D__STDC_FORMAT_MACROS' '-DNDEBUG' '-DNVALGRIND' '-DDYNAMIC_ANNOTATIONS_ENABLED=0' -Ithird_party/icu/public/common -Ithird_party/icu/public/i18n -Ithird_party/wtl/include -I. -Ithird_party/mesa/MesaLib/include -Iout/Release/obj/gen/app -Iout/Release/obj/gen/app/app_locale_settings -Iout/Release/obj/gen/app/app_strings -Iout/Release/obj/gen/app/app_resources -Iskia/config -Ithird_party/skia/include/config -Ithird_party/skia/include/core -Ithird_party/skia/include/effects -Iskia/ext -Ithird_party/harfbuzz/src -Ithird_party/harfbuzz/contrib -MMD -MF out/Release/.deps/out/Release/obj.target/views/views/background.o.d.raw -c -o out/Release/obj.target/views/views/background.o views/background.cc
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: warning: cannot scan executable section 1 of third_party/libvpx/lib/linux/arm-neon/libvpx.a(vp8_dx_iface.c.o) for Cortex-A8 erratum because it has no mapping symbols.
/home/b15608/Chromium/ld: warning: cannot scan executable section 1 of third_party/libvpx/lib/linux/arm-neon/libvpx.a(threading.c.o) for Cortex-A8 erratum because it has no mapping symbols.
/home/b15608/Chromium/ld: warning: cannot scan executable section 1 of third_party/libvpx/lib/linux/arm-neon/libvpx.a(alloccommon.c.o) for Cortex-A8 erratum because it has no mapping symbols.



"/home/b15608/Chromium/ld: error: cannot open : No such file or directory"
What I can not understand is the file can not be opened is ' ', it is very strange.

Could you give me the detailed information of the tool chain you used? Thanks.

If you read our buildbot logs, you'll see this is what we have:

  AR=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-ar
  AS=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-as
  CC=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-gcc
  CXX=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-g++
  GYP_DEFINES=target_arch=arm sysroot=/usr/local/arm-rootfs disable_nacl=1 linux_use_tcmalloc=0 armv7=1 arm_thumb=1 chromeos=1 
  LD=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-ld
  RANLIB=/usr/local/crosstool-trusted/arm-2009q3/bin/arm-none-linux-gnueabi-ranlib

Please remember this is not a help forum. We can't hold your hand and debug your toolchain problem for you.

Thanks for you information.
Please refer to  Issue 47850 :Failing to Build Chromium ARM Version, gold linker is recommended.

This is a known issue with july 18th version of ffmpeg.
It should build with arm, if you disable neon.
remove the 'arm_neon':1,
Hopefully neon will be fixed by the next update (aug 11).

 Issue 49711  has been merged into this issue.

The error
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:28: error: size of array 'x_Y_DC_SCALE' is negative

Appears to be resolved in the Aug 11 version of ffmpeg-mt

Neon specific builds still have this error:

make: *** [out/Release/obj.target/ffmpegsumo/third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.o] Error 1
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:28: error: size of array 'x_Y_DC_SCALE' is negative
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:29: error: size of array 'x_C_DC_SCALE' is negative
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:30: error: size of array 'x_AC_PRED' is negative
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:31: error: size of array 'x_BLOCK_LAST_INDEX' is negative
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:32: error: size of array 'x_INTER_SCANTAB_RASTER_END' is negative
third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:33: error: size of array 'x_H263_AIC' is negative

I wonder if we can just disable building FFmpeg on ARM completely... it's more trouble than its worth at this time.  We might have to disable some tests that rely on FFmpeg to be present.

Or maybe remove the neon config.  We'll have to see!

unsetting 'build_ffmpegsumo%': 0, defined in src/third_party/ffmpeg/
ffmpeg.gyp will skip building ffmpeg.

@fbarchard, @scherkus: I also hit it:

  CC(target) out/Release/obj.target/ffmpegsumo/source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.o
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:28: error: size of array 'x_Y_DC_SCALE' is negative
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:29: error: size of array 'x_C_DC_SCALE' is negative
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:30: error: size of array 'x_AC_PRED' is negative
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:31: error: size of array 'x_BLOCK_LAST_INDEX' is negative
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:32: error: size of array 'x_INTER_SCANTAB_RASTER_END' is negative
source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.c:33: error: size of array 'x_H263_AIC' is negative
make[1]: *** [out/Release/obj.target/ffmpegsumo/source/patched-ffmpeg-mt/libavcodec/arm/mpegvideo_arm.o] Error 1

full logs here:
http://launchpadlibrarian.net/54837440/buildlog_ubuntu-maverick-armel.chromium-codecs-ffmpeg_0.6%2Bsvn20100811r55740%2B56137-0ubuntu1_FAILEDTOBUILD.txt.gz

that's with GYP_DEFINES="disable_sse2=1 target_arch=arm armv7=1
arm_thumb=1 release_extra_cflags=-g use_system_yasm=1 use_system_vpx=1"

it's bad for Ubuntu. We just hit beta1 for 10.10 (Maverick) and it's a regression compared to the previous stable which was usable on ARM. Too bad i didn't catch it before I updated chromium from 5.0.375.127 to 6.0.472.53 in Lucid and Maverick :(

weird. this code is protected by a "#if HAVE_NEON", and HAVE_NEON is only set in the arm-neon headers, which are used only there:

      ['armv7==1 and arm_neon==1', {
        # Need a separate config for arm+neon vs arm
        'ffmpeg_config%': 'arm-neon',

i have armv7=1 but not arm_neon, how could that be??

Arm/Neon appear to be building again, with the sep 09 version of ffmpeg-mt in chromium trunk.

ffmpeg doesnot build in latest trunk on arm,

error:
while linking libffmpegsumo.so,  
symbol av_opt_find in version LIBAVCODEC_52 not defined

Chrome Version (from the about:version page): latest chromium
Is this the most recent version: Yes
OS + version: Linux ARM
CPU architecture (32-bit / 64-bit):32bit
Window manager:
URLs (if relevant):
Behavior in Linux Firefox:
Behavior in Windows Chrome (if you have access to it):

What steps will reproduce the problem?
1.Followed instructions @ http://code.google.com/p/chromium/wiki/LinuxChromiumArm
2.
3.

What is the expected result?
Build Successfully.


What happens instead?
Build breaks

Please provide any additional information below. Attach a screenshot
and backtrace if possible.
1)Build with CodeSourcery toolchain
Error Log: 
collect2: ld terminated with signal 11 [Segmentation fault]

2)Build with gold linker
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
/home/b15608/Chromium/ld: error: cannot open : No such file or directory
collect2: ld returned 1 exit status
make: *** [out/Release/obj.target/third_party/ffmpeg/libffmpegsumo.so]

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.