[Bug 758619] Re: Debug libraries that put their debug infos into a multiarch directory
Hi Steve, I'm not sure what I saw back then. You are right, GDB is able to find the debug infos. Sorry for the noise. ** Changed in: gdb (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758619 Title: Debug libraries that put their debug infos into a multiarch directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758619] [NEW] Debug libraries that put their debug infos into a multiarch directory
Public bug reported: Binary package hint: gdb I'm facing issues when debugging into a glibc call on Natty. The ARM version of the libc6 ddeb (libc6-dbgsym) put its files into /usr/lib/debug/lib/arm-linux-gnueabi. The gdb (7.2-1ubuntu11) is configured with prefix=/usr and doesn't know about the Ubuntu/Debian way of multiarch and thus won't find the debug infos: (gdb) show debug-file-directory The directory where separate debug symbols are searched for is "/usr/lib/debug". As a workaround I set the debug-file-directory to /usr/lib/debug/lib /arm-linux-gnueabi but it didn't work for some reasons. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758619 Title: Debug libraries that put their debug infos into a multiarch directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721531] Re: [armel] gcc computes wrong address for main() at build time
As shown above this bug makes it a bit difficult to obtain the thumb marker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721531 Title: [armel] gcc computes wrong address for main() at build time -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721531] Re: [armel] gcc computes wrong address for main() at build time
I see a very similar issue even with -O0 when using GCC 4.5.2-8ubuntu1
on my ARM board.
Here is a simple test:
$ cat test.c && gcc -O0 -Wall -Winline test.c -o test.bin && echo "O0:" &&
./test.bin && gcc -O2 -Wall -Winline test.c -o test.bin && echo "O2:" &&
./test.bin
#include
static long __attribute__ ((noinline))
getfp (void *p)
{
return (long) p;
}
static void __attribute__ ((noinline))
myfunc(long fp, long foo, long bar, long code, long thumb, long thumb2)
{
printf ("\tfp: 0x%lx\n", fp);
printf ("\tfoo:0x%lx\n", foo);
printf ("\tbar:0x%lx\n", bar);
printf ("\tcode: 0x%lx\n", code);
printf ("\tthumb: 0x%lx\n", thumb);
printf ("\tthumb2: 0x%lx\n", thumb2);
}
int main()
{
long fp = (long) myfunc;
long foo = fp & 0x1L;
long bar = getfp (myfunc);
long code = (long) myfunc & ~0x1L;
long thumb = (long) myfunc & 0x1L;
long thumb2 = getfp (myfunc) & 0x1L;
myfunc(fp, foo, bar, code, thumb, thumb2);
return 0;
}
O0:
fp: 0x83b1
foo:0x1
bar:0x83b1
code: 0x83b0
thumb: 0x0
thumb2: 0x1
O2:
fp: 0x83a1
foo:0x0
bar:0x83a1
code: 0x83a0
thumb: 0x0
thumb2: 0x1
The interesting thing is the " (long) myfunc & 0x1L".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721531
Title:
[armel] gcc computes wrong address for main() at build time
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744458] [NEW] hw perfevents on the pandabaord
Public bug reported: The 2.6.38-1001-linaro-omap kernel reports "unable to reserve pmu" when attempting to access hw counters using perf: $ uname -a Linux panda 2.6.38-1001-linaro-omap #2-Ubuntu SMP Mon Mar 21 21:40:07 UTC 2011 armv7l armv7l armv7l GNU/Linux $ sudo su -c "echo -1 > /proc/sys/kernel/perf_event_paranoid" && cat /proc/sys/kernel/perf_event_paranoid -1 $ sudo ./perf stat -e r63 -- sleep 1 No permission to collect stats. Consider tweaking /proc/sys/kernel/perf_event_paranoid. $ dmesg | tail -1 [10985.304809] hw perfevents: unable to reserve pmu $ sudo su -c "strace -e trace=perf_event_open ./perf stat -e r63 -- sleep 1" perf_event_open(0x1ed338, 0x114c, 0x, 0x, 0) = -1 ENODEV (No such device) The perf_event_open syscall returns ENODEV but the kernel config looks sane to me: $ grep -i perf_ /boot/config-2.6.38-1001-linaro-omap # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_HW_PERF_EVENTS=y CONFIG_PERF_COUNTERS=y CONFIG_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y ** Affects: linux-linaro-omap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744458 Title: hw perfevents on the pandabaord -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
Is there any chance to put the workaround/patch into the Linaro omap4 kernel as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728565] Re: open("/dev/ttyO2", O_RDONLY) never returns on the 2.6.38-1000-linaro-omap
I've got the Oops but only once. It looked very similar to what David
posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728565
Title:
open("/dev/ttyO2", O_RDONLY) never returns on the 2.6.38-1000-linaro-
omap
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728565] [NEW] open("/dev/ttyO2", O_RDONLY) never returns on the 2.6.38-1000-linaro-omap
Public bug reported:
When using the 2.6.38-1000-linaro-omap kernel the process hangs as the
open call never returns. Here is a small testcase:
#include
#include
#include
#include
#include
int main (int argc, char **argv){
int fd;
fd = open("/dev/ttyO2", O_RDONLY);
if (fd == -1) {
perror ("open failed");
exit(EXIT_FAILURE);
}
close(fd);
return 0;
}
Here is the stack trace of this task:
[ 651.671020] openS c059b724 0 642532 0x
[ 651.671051] [] (schedule+0x3f4/0x778) from []
(tty_port_block_til_ready+0x138/0x2f4)
[ 651.671081] [] (tty_port_block_til_ready+0x138/0x2f4) from
[] (tty_open+0x178/0x420)
[ 651.671081] [] (tty_open+0x178/0x420) from []
(chrdev_open+0x114/0x1ec)
[ 651.671112] [] (chrdev_open+0x114/0x1ec) from []
(__dentry_open+0x100/0x2b8)
[ 651.671142] [] (__dentry_open+0x100/0x2b8) from []
(nameidata_to_filp+0x60/0x68)
[ 651.671142] [] (nameidata_to_filp+0x60/0x68) from []
(finish_open+0xa0/0x174)
[ 651.671173] [] (finish_open+0xa0/0x174) from []
(do_filp_open+0x18c/0x5f8)
[ 651.671173] [] (do_filp_open+0x18c/0x5f8) from []
(do_sys_open+0x5c/0x138)
[ 651.671203] [] (do_sys_open+0x5c/0x138) from []
(ret_fast_syscall+0x0/0x30)
** Affects: linux-linaro (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- open("/dev/ttyO2", O_RDONLY) returns on the 2.6.38-1000-linaro-omap
+ open("/dev/ttyO2", O_RDONLY) never returns on the 2.6.38-1000-linaro-omap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728565
Title:
open("/dev/ttyO2", O_RDONLY) never returns on the 2.6.38-1000-linaro-
omap
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720055] Re: Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8
I can also confirm that the 2.6.38-1000-linaro-omap kernel works on my panda. I'm using the hwpack_linaro- panda_20110303-0_armel_supported.tar.gz with the linaro-n-developer- tar-20110303-0.tar.gz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720055 Title: Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604753] Re: [eglibc] process shared mutex's fail on armel v7 (thumb)
I think this the issue has been fixed by #643171. I do not see this testcase failing using a recent (e)glibc and GCC. Could anyone of the original reporters check if it works for them? Please make sure that you use at least glibc 2.12.1-0ubuntu11 and GCC 4.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604753 Title: [eglibc] process shared mutex's fail on armel v7 (thumb) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720055] Re: Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8
I can reproduce the error on my board (every boot fails at the same place) but the addresses change. The error occurs right before the OMAP components are initialized (DSS, DISPC, DSI, DSI2). It doesn't matter if I build the kernel myself or use a recent prebuild kernel from a hwpack (e.g. 20110218). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/720055 Title: Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721147] Re: flash-kernel subarch check fails with Linaro OMAP kernels
** Branch linked: lp:~kwerner/flash-kernel/lp-721147 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721147 Title: flash-kernel subarch check fails with Linaro OMAP kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721147] Re: flash-kernel subarch check fails with Linaro OMAP kernels
** Patch added: "flash-kernel_linaro-omap.patch" https://bugs.launchpad.net/bugs/721147/+attachment/1857303/+files/flash-kernel_linaro-omap.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721147 Title: flash-kernel subarch check fails with Linaro OMAP kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721147] [NEW] flash-kernel subarch check fails with Linaro OMAP kernels
Public bug reported: Binary package hint: flash-kernel When using flash-kernel with a recent Linaro kernel on an OMAP4 board the subarch check fails because the kfile does not end with a '3' or '4' - it's just named like this: vmlinuz-2.6.37-1002-linaro-omap. Since the linaro-omap kernel supports both the OMAP3 and OMAP4 there is no need to add a '3' or '4'. The attached patch omits the check_subarch check for OMAP boards if $kfile matches the substring 'linaro-omap'. ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Tags: linaro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721147 Title: flash-kernel subarch check fails with Linaro OMAP kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
@warmcat Your patch fixes the issue on my board. I've applied your patch to the linaro natty kernel and the system stays alive. kernel: http://git.linaro.org/gitweb?p=ubuntu/linux-linaro- natty.git;a=commit;h=ab75502a50e83d38a2b7892ff81f63decf5fb363 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604753] Re: [eglibc] process shared mutex's fail on armel v7 (thumb)
I ran the apr testsuite (svn revision 1071306) several times and I notice that the testlock:test_timeoutcond test fails sometimes because the timer returned to late. Not sure sure if this is related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604753 Title: [eglibc] process shared mutex's fail on armel v7 (thumb) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604753] Re: [eglibc] process shared mutex's fail on armel v7 (thumb)
I ran the testprocmutex test on a panda board using ubuntu natty alpha 2 and it passed: $ ./testall testprocmutex testprocmutex : SUCCESS All tests passed. $ apt-cache show libc6 gcc|grep Version Version: 4:4.5.1-1ubuntu3 Version: 2.12.1-0ubuntu16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604753 Title: [eglibc] process shared mutex's fail on armel v7 (thumb) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604753] Re: [eglibc] process shared mutex's fail on armel v7 (thumb)
I had a quick look into the apr sources. Their locks/unix/proc_mutex.c can map the proc_mutex functionality to various methods: 1) Posix sem implemenation (see mutex_posixsem_methods) 2) SysV sem implementation (see mutex_sysv_methods) 3) pthread implementation (see mutex_proc_pthread_methods) 4) fcntl implementation(see mutex_fcntl_methods) 5) flock implementation(see mutex_flock_methods) I think only the pthread implemenation (3) is of interest here. The creation of the pthread_mutex happens at: locks/unix/proc_mutex.c:proc_mutex_proc_pthread_create that calls pthread_mutex_init with the following attributes: PTHREAD_PROCESS_SHARED, PTHREAD_MUTEX_ROBUST_NP, PTHREAD_PRIO_INHERIT The apr-phthread-mutex functionality relies on pthread_mutex_lock and pthread_mutex_trylock. The eglibc implemenation for such a mutex calls atomic_compare_and_exchange_val_acq (see also lll_lock/lll_trylock at ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.h) which goes down to __arch_compare_and_exchange_val_32_acq. Using (e)glibc (>= 2.12.1-0ubuntu11) and GCC (>=4.5) this expands to __sync_val_compare_and_swap (ports/sysdeps/unix/sysv/linux/arm/nptl/bits/atomic.h) which should be safe even on a SMP system. Some infos regarding the atomic memory operations can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/AtomicMemoryOperations#implementation%20details The next step would be to check whether the testcase fails using a decent GCC and eglibc (Ubuntu Natty for example). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604753 Title: [eglibc] process shared mutex's fail on armel v7 (thumb) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
@warmcat Thanks for the LED heartbeat hint. I've added ledtrig-heartbeat to /etc/modules and I see that the Status1-LED begins to flash during boot. When the system dies (shortly after it gets to the bash prompt on my board) the LED stays off and the CPU cools down. The board works fine as soon as I replace the linaro kernel (uImage + uInitrd) with the files from the Ubuntu Natty alpha2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
To check if it's x-loader/u-boot related I replaced the MLO and u-boot.bin of the 20110214 Linaro snapshot with the files from the working Ubuntu Natty alpha2 installation but that didn't change anything - the board still goes off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
The latest (20110214) Linaro headless snapshot plus corresponding hwpack still powers down my pandaboard shortly after it gets to the bash boot. As Paul said this seems to be independent of the attached devices (HDMI, USB, Ethernet). To check if it's related to something that is started by upstart I added "init=/bin/bash" to the bootargs but the board still dies (shortly after the regulator_init_complete msgs). Then I copied over the uImage + uInitrd from the Ubuntu Natty alpha2 and the system works fine. Unfortunately the Ubuntu kernel (2.6.35-1101-omap4) differs a lot from current Linaro kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
@Aneesh
Thanks for looking into this. I can reproduce this bug on my A1 ES2.1 8-layer
750-2152-010(D) board. H ere are the details:
$ for gpio in 171 101 182; do read gpio${gpio} <
/sys/class/gpio/gpio${gpio}/value; done && echo "Revision: ${gpio171}
${gpio101} ${gpio182}"
Revision: 0 1 1
$ sudo ./devmem2 0x4A002204
/dev/mem opened.
Memory mapped at address 0x40155000.
Value at address 0x4A002204 (0x40155204): 0x3B95C02F
I'm using the following PSU:
http://search.digikey.com/scripts/DkSearch/dksus.dll?KeyWords=T951-P5P-ND
I've tried several linaro-n snapshots on this board - all showed the same
behavior. Also the alpha-2 doesn't work for me. These are the files used for
the image creation:
* linaro-natty-headless-tar-20110203-1.tar.gz
* hwpack_linaro-panda_20110203-0_armel_supported.tar.gz
I'm using l-m-c from lp:linaro-image-tools rev 287 with the qemu-kvm-
extras-static from Natty (0.13.0+noroms-0ubuntu11_i386.deb) on a i686
Maverick installation.
Please let me know if you need further details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708883
Title:
Panda board shuts down during boot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708883] Re: Panda board shuts down during boot
I've tried various hwpacks and (headless) images and encountered exact the same issue while the Ubuntu 10.10 image works flawlessly on this board. In order to exclude faulty external components I used different power supplies and several SD cards - also no difference. My next step was to use a SD-card image that works works on a PandaBoard of a colleague (20110127 hwpack with 20110126 headless) to exclude differences during the creation of the image (version of l-m-c and such). On my board it shows the same symptoms as the image I created myself. > I do not see this problem when booting in the validation lab with old > uboot/xloader + new everything else This is interesting. I took the Ubuntu 10.10 image which runs fine on my board and replaced only the kernel with git://git.linaro.org/ubuntu/linux-linaro-natty.git with the result that the board shuts down. Therefore I thought it's related to the Linaro kernel. Could you elaborate which uboot/xloader you used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708883 Title: Panda board shuts down during boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659713] Re: armel build failures 20101012
With these two patches applied, the GCC trunk r167715 bootstrapped fine on the vexpress: * http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00915.html (PR46040: crtstuff.c:308:26: error: '__DTOR_LIST__' undeclared) * http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00402.html (PR46667: libstdc++ section type conflict during) I enabled the c and c++ languages only: === gcc Summary === # of expected passes73379 # of unexpected failures229 # of unexpected successes 7 # of expected failures 202 # of unresolved testcases 2 # of unsupported tests 949 === g++ Summary === # of expected passes25775 # of unexpected failures19 # of unexpected successes 1 # of expected failures 156 # of unsupported tests 374 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659713 Title: armel build failures 20101012 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643171] Re: Use the __sync primitives in EGLIBC
The patch was accepted upstream and has been committed. ** Changed in: linaro-toolchain-misc Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/643171 Title: Use the __sync primitives in EGLIBC -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659713] Re: armel build failures 20101012
I just tried to compile r167352 from the GCC svn and encountered the very same issue. Therefore I applied the patch from #46040. After restricting the build to the C language only it finishes but I see the same testsuite failures as Matthias described in comment #10. In case C++ is enabled the build of the libstdc++ fails with: make[4]: Entering directory `/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/src' /bin/bash ../libtool --tag CXX --mode=compile /home/kwerner/data/gcc-build/./gcc/xgcc -shared-libgcc -B/home/kwerner/data/gcc-build/./gcc -nostdinc++ -L/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/src -L/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/src/.libs -B/home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/bin/ -B/home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/lib/ -isystem /home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/include -isystem /home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/sys-include -I/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/armv7l-unknown-linux-gnueabi -I/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include -I/home/kwerner/data/gcc/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2 -D_GNU_SOURCE -c -o pool_allocator.lo ../../../../gcc/libstdc++-v3/src/pool_allocator.cc libtool: compile: /home/kwerner/data/gcc-build/./gcc/xgcc -shared-libgcc -B/home/kwerner/data/gcc-build/./gcc -nostdinc++ -L/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/src -L/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/src/.libs -B/home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/bin/ -B/home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/lib/ -isystem /home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/include -isystem /home/kwerner/data/gcc-install/armv7l-unknown-linux-gnueabi/sys-include -I/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/armv7l-unknown-linux-gnueabi -I/home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include -I/home/kwerner/data/gcc/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g -O2 -D_GNU_SOURCE -c ../../../../gcc/libstdc++-v3/src/pool_allocator.cc -fPIC -DPIC -o .libs/pool_allocator.o In file included from /home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/armv7l-unknown-linux-gnueabi/bits/gthr.h:162:0, from /home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/ext/atomicity.h:34, from /home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/ext/pool_allocator.h:50, from ../../../../gcc/libstdc++-v3/src/pool_allocator.cc:31: /home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/ext/concurrence.h: In destructor '__gnu_cxx::__scoped_lock::~__scoped_lock()': /home/kwerner/data/gcc-build/armv7l-unknown-linux-gnueabi/libstdc++-v3/include/ext/concurrence.h:313:5: error: __gnu_cxx::__scoped_lock::~__scoped_lock() causes a section type conflict A comment from Ramana Radhakrishnan seems to confirm this: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46667#c4 ** Bug watch added: GCC Bugzilla #46667 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46667 -- armel build failures 20101012 https://bugs.launchpad.net/bugs/659713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643171] Re: Use the __sync primitives in EGLIBC
** Changed in: linaro-toolchain-misc Status: Confirmed => In Progress -- Use the __sync primitives in EGLIBC https://bugs.launchpad.net/bugs/643171 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
