Re: Questions on .config [uClibc for ARM Cortex A9]

2013-03-15 Thread Sergei Poselenov
Hello Ramesh,

The following settings work for me (I'm building for Cortex-M3/Thumb):
make -s ARCH_CFLAGS= 'CPU_CFLAGS=-mthumb -march=armv7 -mfix-cortex-m3-ldrd'

Note the space between ARCH_CFLAGS= and the rest of the string.

Regards,
Sergei

On Thu, 14 Mar 2013 02:44:26 +
Ramesh Rangavittal ramesh.rangavit...@ruckuswireless.com wrote:

 Hello,
 
 I am trying to build uClibc for ARM Cortex A9 processor.  For the version
 uClibc-0.9.30.1  powerpc e500, I see the below config options set in
 a .config found a different email thread.
 
 CONFIG_E500=y
 TARGET_SUBARCH=e500
 
 For the A9,   I ran into the below email thread, I am not sure what value
 should be set?
 
 http://lists.uclibc.org/pipermail/uclibc/2011-February/044737.html
 
 Can someone please advice. Any pointers to a README doc to have the right
 settings for this processor is highly appreciated. BTW the uClibc version
 that I am trying build is uclibc-0.9.33.2.
 
 /Ramesh
 
 
 ___
 uClibc mailing list
 uClibc@uclibc.org
 http://lists.busybox.net/mailman/listinfo/uclibc



-- 
Emcraft Systems - uClinux for Cortex-M MCUs | www.emcraft.com | s...@emcraft.com

___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


segfault of test on buildroot system

2013-03-15 Thread Alexander Varnin

Hello.
I'm using buildroot based system with ARM samsung processor (s3c2443).
I've found a case, when i get segfault in my application. Using x86 
debian compilers doesn't reproduce error.
Attaching test program to this letter. There is an exception getting 
throw from constructor of child-class (DisplayPassDevice). At that time 
parent destructor (~PassageDevice) getting called. When exiting from 
parent destructor i got segfault.

# ./throw
~PassageDevice
Aborted (core dumped)

One more necessary condition. The bug appears only when i compile my 
code with pthread:

../minipos-OS-build/host/usr/bin/arm-linux-g++ throw.cpp -o throw -lpthread

When i compile without -lpthread flag, program works OK.
# ./throw
~PassageDevice
catched

I don't know what does this problem belongs to, so i write there for 
help. Probably you'll just point me, where to report it.

Software i use is following: gcc 4.5.4, uClibc 0.9.33.2, linux 3.6.

#include stdio.h
#include stdexcept

class PassageDevice
{
public:
virtual void OnPassageOpen() = 0;
virtual void OnPassageClose() = 0;
virtual ~PassageDevice() 
{
	printf(~PassageDevice\n);
}
};

class DisplayPassDevice: public PassageDevice
{
public:
class Exception {};

DisplayPassDevice(void * config) 
{
throw Exception();
}
~DisplayPassDevice() 
{
	printf(~DisplayPassDevice\n);
}

virtual void OnPassageOpen() {printf(OnPassageOpen\n);}
virtual void OnPassageClose() {printf(OnPassageClose\n);}
};


DisplayPassDevice * disp=0;

int main()
{
try {
disp = new DisplayPassDevice(0);
} catch(DisplayPassDevice::Exception) {
printf(catched\n );
return 1;
}
return 0;
}

___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc

uClibc trunk broken

2013-03-15 Thread Vineet Gupta
Hi Bernhard,

It seems that 950fcf0f68732a9aafaIt inet: res_nclose: free user-buffer breaks
the build. This is on ARC port with linthreads.old

-8-
In file included from libc/inet/res_init.c:8:
libc/inet/resolv.c: In function '__res_iclose':
libc/inet/resolv.c:3539: error: '__resp' undeclared (first use in this function)
libc/inet/resolv.c:3539: error: (Each undeclared identifier is reported only 
once
libc/inet/resolv.c:3539: error: for each function it appears in.)
make: *** [libc/inet/res_init.os] Error 1
-8-

Reverting the above commit makes the build go thru.
I don't have a fix handy but though of reporting anyways !

Thx,
-Vineet
___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


RE: uclibc 3.3.2 with gcc-4.7

2013-03-15 Thread Alexander Varnin

I've faced problem mentioned in this half-year old thread

http://lists.uclibc.org/pipermail/uclibc/2012-August/046997.html

Is there any suggestions, what to do, to fix it?
___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


Re: uClibc trunk broken

2013-03-15 Thread Bernhard Reutner-Fischer

On 15 March 2013 12:53:55 Vineet Gupta vineet.gup...@synopsys.com wrote:

Hi Bernhard,

It seems that 950fcf0f68732a9aafaIt inet: res_nclose: free user-buffer breaks
the build. This is on ARC port with linthreads.old

-8-
In file included from libc/inet/res_init.c:8:
libc/inet/resolv.c: In function '__res_iclose':
libc/inet/resolv.c:3539: error: '__resp' undeclared (first use in this 
function)


Yes, that should read __res_state() instead.
Can you confirm this?

Thanks,


Sent with AquaMail for Android
http://www.aqua-mail.com


___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


Re: segfault of test on buildroot system

2013-03-15 Thread Khem Raj
On Friday, March 15, 2013, Alexander Varnin fenix...@mail.ru wrote:
 Hello.
 I'm using buildroot based system with ARM samsung processor (s3c2443).
 I've found a case, when i get segfault in my application. Using x86
debian compilers doesn't reproduce error.
 Attaching test program to this letter. There is an exception getting
throw from constructor of child-class (DisplayPassDevice). At that time
parent destructor (~PassageDevice) getting called. When exiting from parent
destructor i got segfault.
 # ./throw
 ~PassageDevice
 Aborted (core dumped)

 One more necessary condition. The bug appears only when i compile my code
with pthread:
 ../minipos-OS-build/host/usr/bin/arm-linux-g++ throw.cpp -o throw
-lpthread

Do you use old abi by any chance?

 When i compile without -lpthread flag, program works OK.
 # ./throw
 ~PassageDevice
 catched

 I don't know what does this problem belongs to, so i write there for
help. Probably you'll just point me, where to report it.
 Software i use is following: gcc 4.5.4, uClibc 0.9.33.2, linux 3.6.


___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


RE: Questions on .config [uClibc for ARM Cortex A9]

2013-03-15 Thread Ramesh Rangavittal

From: Sergei Poselenov [sposele...@emcraft.com]
Sent: Friday, March 15, 2013 1:50 AM
To: Ramesh Rangavittal
Cc: uclibc@uclibc.org
Subject: Re: Questions on .config  [uClibc for ARM Cortex A9]

Hello Ramesh,

The following settings work for me (I'm building for Cortex-M3/Thumb):
make -s ARCH_CFLAGS= 'CPU_CFLAGS=-mthumb -march=armv7 -mfix-cortex-m3-ldrd'

Note the space between ARCH_CFLAGS= and the rest of the string.

Regards,
Sergei

On Thu, 14 Mar 2013 02:44:26 +
Ramesh Rangavittal ramesh.rangavit...@ruckuswireless.com wrote:

 Hello,

 I am trying to build uClibc for ARM Cortex A9 processor.  For the version
 uClibc-0.9.30.1  powerpc e500, I see the below config options set in
 a .config found a different email thread.

 CONFIG_E500=y
 TARGET_SUBARCH=e500

 For the A9,   I ran into the below email thread, I am not sure what value
 should be set?

 http://lists.uclibc.org/pipermail/uclibc/2011-February/044737.html

 Can someone please advice. Any pointers to a README doc to have the right
 settings for this processor is highly appreciated. BTW the uClibc version
 that I am trying build is uclibc-0.9.33.2.

 /Ramesh


 ___
 uClibc mailing list
 uClibc@uclibc.org
 http://lists.busybox.net/mailman/listinfo/uclibc



--
Emcraft Systems - uClinux for Cortex-M MCUs | www.emcraft.com | s...@emcraft.com

=

Thank you Bernhard  Sergei for the answers. 

Our build infrastructure is based on uClibc 0.9.30.1   I am wondering if I 
really need to use the latest version at this point (0.9.33.2) or  0.9.30.1 
itself is good for the a9 processor.  

Regards
Ramesh

___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


Re: Questions on .config [uClibc for ARM Cortex A9]

2013-03-15 Thread Carmelo AMOROSO
On 15/03/2013 17.15, Ramesh Rangavittal wrote:
 
 From: Sergei Poselenov [sposele...@emcraft.com]
 Sent: Friday, March 15, 2013 1:50 AM
 To: Ramesh Rangavittal
 Cc: uclibc@uclibc.org
 Subject: Re: Questions on .config  [uClibc for ARM Cortex A9]
 
 Hello Ramesh,
 
 The following settings work for me (I'm building for Cortex-M3/Thumb):
 make -s ARCH_CFLAGS= 'CPU_CFLAGS=-mthumb -march=armv7 -mfix-cortex-m3-ldrd'
 
 Note the space between ARCH_CFLAGS= and the rest of the string.
 
 Regards,
 Sergei
 
 On Thu, 14 Mar 2013 02:44:26 +
 Ramesh Rangavittal ramesh.rangavit...@ruckuswireless.com wrote:
 
 Hello,

 I am trying to build uClibc for ARM Cortex A9 processor.  For the version
 uClibc-0.9.30.1  powerpc e500, I see the below config options set in
 a .config found a different email thread.

 CONFIG_E500=y
 TARGET_SUBARCH=e500

 For the A9,   I ran into the below email thread, I am not sure what value
 should be set?

 http://lists.uclibc.org/pipermail/uclibc/2011-February/044737.html

 Can someone please advice. Any pointers to a README doc to have the right
 settings for this processor is highly appreciated. BTW the uClibc version
 that I am trying build is uclibc-0.9.33.2.

 /Ramesh


 ___
 uClibc mailing list
 uClibc@uclibc.org
 http://lists.busybox.net/mailman/listinfo/uclibc
 
 
 
 --
 Emcraft Systems - uClinux for Cortex-M MCUs | www.emcraft.com | 
 s...@emcraft.com
 
 =
 
 Thank you Bernhard  Sergei for the answers. 
 
 Our build infrastructure is based on uClibc 0.9.30.1   I am wondering if I 
 really need to use the latest version at this point (0.9.33.2) or  0.9.30.1 
 itself is good for the a9 processor.  
 

Ramesh, latest is preferrable. We use it successfully on Cortex-A9 in a
very demanding context like STB, Media Sever and Home Gateway.

 Regards
 Ramesh
 

Cheers,
Carmelo

 ___
 uClibc mailing list
 uClibc@uclibc.org
 http://lists.busybox.net/mailman/listinfo/uclibc
 
 

___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc


Re: uClibc trunk broken

2013-03-15 Thread Vineet Gupta
Hi Bernhard,

On Friday 15 March 2013 08:47 PM, Bernhard Reutner-Fischer wrote:
 On 15 March 2013 12:53:55 Vineet Gupta vineet.gup...@synopsys.com wrote:
 Hi Bernhard,

 It seems that 950fcf0f68732a9aafaIt inet: res_nclose: free user-buffer 
 breaks
 the build. This is on ARC port with linthreads.old

 -8-
 In file included from libc/inet/res_init.c:8:
 libc/inet/resolv.c: In function '__res_iclose':
 libc/inet/resolv.c:3539: error: '__resp' undeclared (first use in this 
 function)

 Yes, that should read __res_state() instead.
 Can you confirm this?

Not sure what you mean, there's no function named __res_state()
I suppose it needs to fallback to usage of global _res, something like below


diff --git a/libc/inet/resolv.c b/libc/inet/resolv.c
index 769b65f..290bced 100644
--- a/libc/inet/resolv.c
+++ b/libc/inet/resolv.c
@@ -3536,7 +3536,7 @@ __res_iclose(res_state statp)
struct __res_state * rp = statp;
__UCLIBC_MUTEX_LOCK(__resolv_lock);
if (rp == NULL)
-   rp = __resp;
+   rp = _res;
__close_nameservers();
__res_sync = NULL;
 #ifdef __UCLIBC_HAS_IPV6__

That seems to build 

-Vineet
___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc