bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/20238] New: error: undefined reference to '__cxa_finalize'


From: jorgeayrespereira at hotmail dot com
Subject: [Bug ld/20238] New: error: undefined reference to '__cxa_finalize'
Date: Fri, 10 Jun 2016 11:47:20 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=20238

            Bug ID: 20238
           Summary: error: undefined reference to '__cxa_finalize'
           Product: binutils
           Version: 2.27 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: jorgeayrespereira at hotmail dot com
  Target Milestone: ---

so)
target SharedLib: libkeymaster_messages
(/home/jorge/cm13/out/target/product/bacon/obj/SHARED_LIBRARIES/libkeymaster_messages_intermediates/LINKED/libkeymaster_messages.so)
/home/jorge/cm13/out/target/product/bacon/obj/lib/libdl.so: error: undefined
reference to '__cxa_finalize'
collect2: error: ld returned 1 exit status
build/core/executable_internal.mk:79: recipe for target
'/home/jorge/cm13/out/target/product/bacon/obj/EXECUTABLES/fsck_msdos_intermediates/LINKED/fsck_msdos'
failed
make: ***
[/home/jorge/cm13/out/target/product/bacon/obj/EXECUTABLES/fsck_msdos_intermediates/LINKED/fsck_ms


Hello. This is already present for a while, and I have been waiting for a fix.
I compile custom gcc to use on android roms.  When I compile the new gcc with
your head branch and after use it on android source I get this error. This
wasn't present on versions before 23st March. After merging on 1st April I
started to get this errors.

When I use your 2.25/2.26 everything goes fine. So I suppose this is a bug of
the master branch?

I didn't report earlier since i thought this would be fixed meanwhile. The
source used on android was from MarshMallow version (including the latest
revision).

Thanks

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]