mono ftbfs with thumb2 on armel

Bug #514215 reported by Alexander Sack
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Fix Released
Critical
Unassigned
Nominated for Jaunty by r12056
Nominated for Karmic by r12056
Lucid
Fix Released
Critical
Unassigned

Bug Description

Binary package hint: mono

ftbfs:

https://edge.launchpad.net/ubuntu/+source/mono/2.4.3+dfsg-1/+build/1472220

should use gcc atomics

libtool: compile: gcc -DPACKAGE_NAME=\"libgc-mono\" -DPACKAGE_TARNAME=\"libgc-mono\" -DPACKAGE_VERSION=\"6.6\" "-DPACKAGE_STRING=\"libgc-mono 6.6\"" -DPACKAGE_BUGREPORT=\"<email address hidden>\" -DPACKAGE_URL=\"\" -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1 -D_IN_LIBGC=1 -I./.. -I./.. -I./include -DGC_LINUX_THREADS -D_GNU_SOURCE -D_REENTRANT -DUSE_MMAP -DUSE_MUNMAP -D_FILE_OFFSET_BITS=64 -DARM_FPU_NONE=1 -DNO_UNALIGNED_ACCESS -g -O2 -O2 -g -g -MT alloc.lo -MD -MP -MF .deps/alloc.Tpo -c alloc.c -fPIC -DPIC -o .libs/alloc.o
/tmp/ccw6KlFy.s: Assembler messages:
/tmp/ccw6KlFy.s:1181: Error: selected processor does not support `swp r3,r2,[r1]'
/tmp/ccw6KlFy.s:2607: Error: selected processor does not support `swp r3,r2,[r1]'
/tmp/ccw6KlFy.s:3360: Error: selected processor does not support `swp r3,r2,[r1]'

Tags: armel armv7 thumb

Related branches

Revision history for this message
Alexander Sack (asac) wrote :

targetting/milestoning ... as it breaks arm images because of arch all/any out of sync

Changed in mono (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
Changed in mono (Ubuntu Lucid):
milestone: none → lucid-alpha-3
milestone: lucid-alpha-3 → none
Revision history for this message
Alexander Sack (asac) wrote :

linked this bug to thumb2 review page: https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList

Alexander Sack (asac)
description: updated
tags: added: armel armv7
Revision history for this message
Paul Larson (pwlars) wrote :

I think the intention was to keep the milestone after targetting, right? re-adding

Changed in mono (Ubuntu Lucid):
milestone: none → lucid-alpha-3
Revision history for this message
Paul Larson (pwlars) wrote :

From a duplicate bug that concerned porting mono to thumb2:
https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList

"needs investigation - has atomic implementation and mov's"

Alexander Sack (asac)
Changed in mono (Ubuntu Lucid):
status: Triaged → Fix Released
Alexander Sack (asac)
Changed in mono (Ubuntu Lucid):
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mono - 2.4.4~svn151842-1ubuntu1

---------------
mono (2.4.4~svn151842-1ubuntu1) lucid; urgency=low

  [ Iain Lane <email address hidden> ]
  * Merge from Debian unstable, remaining changes:
    + fix mono ftbfs with thumb2 on armel; use gcc atomic built-ins. Please
      note that this change has been applied in the Debian packaging branch,
      so should be dropped after the next upload there. (LP: #525063)

  [ Alexander Sack <email address hidden> ]
  * mono-thumb2-jit-blx.dpatch, 00list: add fix for more thumb2
    porting issues (LP: #514215)

mono (2.4.4~svn151842-1) unstable; urgency=medium

  [ Jo Shields ]
  * debian/patches/dont_assert_on_empty_DGC_field_r146984.dpatch:
    + Backport fix from upstream which causes IKVM to fail to build
      (Closes: #562393)
  * debian/patches/escape_Lucene.Net_search_string_r148946.dpatch:
    + Backport fix from upsrream which causes Monodoc to crash when
      searching for "()" and other characters (Closes: #516597)

  [ Mirco Bauer ]
  * The "Mono 2.4.4 FREE LUV for squeeze & lucid" release
  * New upstream SVN snapshot of the mono-2-4 branch
    + Fixed assertion failed in fieldref_encode_signature which caused
      SIGABRT. (Closes: #565548)
    + Mono is now DFSG complaint again by default as the binary-only shipped
      files were replaced with source code. Also the non-free XML
      specification files were replaced and thus we can ship the RabbitMQ
      library again.
  * debian/patches/disable_building_convert.exe.dpatch
    debian/patches/disable_building_RabbitMQ.Client.dll.dpatch:
    + Dropped, we can build the RabbitMQ client library and convert.exe again,
      as the source is provided now (see above).
  * debian/fix_large_ranges_in_random_generator_r146995.dpatch:
    + Dropped, already applied upstream.
  * debian/watch:
    + We are only watching the 2.4 series for now (until squeeze is released)
  * debian/control:
    + Added libnunit-cil-dev to Depends of libmono-cil-dev as that one
      contains the symlink to the nunit.pc file which is no longer present in
      libnunit2.4-cil but libnunit-cil-dev.
    + Dropped purpose less libmono-nunit2.4-cil package as libmono-cil-dev
      does the job now.
    + Added conflicts libmono-nunit2.4-cil to libmono-cil-dev for cleaning up.
    + Shortened too long line in the long descroption of libmono-cil-dev.
    + Changed section of libmono-dev to libdevel.
    + Added ${misc:Depends} to Depends of all packages.
    + Bumped Standards-Version to 3.8.4 (no changes needed).
    + Re-added libmono-messaging-rabbitmq2.0-cil and libmono-rabbitmq2.0-cil
      packages.
  * debian/cli.binfmt:
    + Replaced mono-common with mono-runtime. (Closes: #565490)
  * debian/mono-runtime.postinst:
    + Removed obsolete mono-common / mono-jit traces.
  * debian/copyright:
    + Refere to versioned GPL license file.
    + Updated license information of RabbitMQ XML specification files.
    + Added license information of docs/HtmlAgilityPack.
 -- Alexander Sack <email address hidden> Mon, 22 Feb 2010 23:51:28 +0100

Changed in mono (Ubuntu Lucid):
status: Fix Committed → Fix Released
Loïc Minier (lool)
tags: added: thumb
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.