Re: RTEMS Toolchain building failed for ARM

[zhang heng]

Dear,
heng@heng-PC MINGW64 /h/Project/rtems/rsb/rtems
$ pacman -Q  mingw-w64-x86_64-gcc
mingw-w64-x86_64-gcc 6.2.0-2
heng@heng-PC MINGW64 /h/Project/rtems/rsb/rtems
$ gcc  -v
Using built-in specs.
COLLECT_GCC=F:\Program Files (x86)\msys2\mingw64\bin\gcc.exe
COLLECT_LTO_WRAPPER=F:/Program\ Files\
(x86)/msys2/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6.2.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../gcc-6.2.0/configure --prefix=/mingw64
--with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32
--host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32
--with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include
--libexecdir=/mingw64/lib --enable-bootstrap --with-arch=x86-64
--with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada
--enable-shared --enable-static --enable-libatomic --enable-threads=posix
--enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes
--disable-libstdcxx-pch --disable-libstdcxx-debug --disable-isl-version-check
--enable-lto --enable-libgomp --disable-multilib --enable-checking=release
--disable-rpath --disable-win32-registry --disable-nls --disable-werror
--disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64
--with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64
--with-pkgversion='Rev2, Built by MSYS2 project'
--with-bugurl=https://sourceforge.net/projects/msys2 --with-gnu-as --with-gnu-ld
Thread model: posix
gcc version 6.2.0 (Rev2, Built by MSYS2 project)

So I  am sure that the GCC have installed according to the above information.
but the error still exist.

configure: loading site script F:/Program Files 
(x86)/msys2/mingw64/etc/config.site
checking build system type... x86_64-w64-mingw32
checking host system type... x86_64-w64-mingw32
checking for x86_64-w64-mingw32-as... no
checking for as... as
checking for x86_64-w64-mingw32-dlltool... no
checking for dlltool... dlltool
checking for x86_64-w64-mingw32-objdump... no
checking for objdump... objdump
checking how to print strings... printf
checking for x86_64-w64-mingw32-gcc... x86_64-w64-mingw32-gcc -O2 -pipe
-I/H/Project/rtems/rsb/rtems/build/tmp/sb-heng/4.11/rtems-arm/H/Project/rtems/4.11/include
checking whether the C compiler works... no
configure: error: in `/H/Project/rtems/rsb/rtems/build/e2xwm1/expat-2.1.0':
configure: error: C compiler cannot create executables
See `config.log' for more details
shell cmd failed: sh -ex  /H/Project/rtems/rsb/rtems/build/e2xwm1/doit
error: building e2xwm1

Thanks,
zhang heng

发自网易邮箱大师
On 2/1/2018 11:10，zhang 
heng wrote：
Dear All,
  I am attempting to build the RTEMS tool set according to RTEMS User Manual 
and Windows Host Tool Chain on windows10, but I meet with some troubles.
  I have done the following commands,

 $ ../source-builder/sb-check
   RTEMS Source Builder - Check, 4.11 (01ac76f2f90f)
   Environment is ok

but it generates an error when I execute such command:

$ ../source-builder/sb-set-builder --prefix=/h/Project/rtems/4.11 --jobs=none 
4.11/rtems-arm
RTEMS Source Builder - Set Builder, 4.11 (4a87913b1451 modified)
Build Set: 4.11/rtems-arm
Build Set: 4.11/rtems-autotools.bset
Build Set: 4.11/rtems-autotools-internal.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-w64-mingw32-1
building: autoconf-2.69-x86_64-w64-mingw32-1
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-w64-mingw32-1
building: automake-1.12.6-x86_64-w64-mingw32-1
cleaning: autoconf-2.69-x86_64-w64-mingw32-1
cleaning: automake-1.12.6-x86_64-w64-mingw32-1
Build Set: Time 0:06:46.911569
Build Set: 4.11/rtems-autotools-base.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-w64-mingw32-1
building: autoconf-2.69-x86_64-w64-mingw32-1
reporting: tools/rtems-autoconf-2.69-1.cfg -> 
autoconf-2.69-x86_64-w64-mingw32-1.txt
reporting: tools/rtems-autoconf-2.69-1.cfg -> 
autoconf-2.69-x86_64-w64-mingw32-1.xml
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-w64-mingw32-1
building: automake-1.12.6-x86_64-w64-mingw32-1
reporting: tools/rtems-automake-1.12.6-1.cfg -> 
automake-1.12.6-x86_64-w64-mingw32-1.txt
reporting: tools/rtems-automake-1.12.6-1.cfg -> 
automake-1.12.6-x86_64-w64-mingw32-1.xml
installing: autoconf-2.69-x86_64-w64-mingw32-1 -> H:\Project\rtems\4.11
installing: automake-1.12.6-x86_64-w64-mingw32-1 -> H:\Project\rtems\4.11
cleaning: autoconf-2.69-x86_64-w64-mingw32-1
cleaning: automake-1.12.6-x86_64-w64-mingw32-1
Build Set: Time 0:06:58.049423
Build Set: Time 0:13:44.968990
config: devel/expat-2.1.0-1.cfg
package: expat-2.1.0-x86_64-w64-mingw32-1
building: expat-2.1.0-x86_64-w64-mingw32-1
error: building e2xwm1
Build FAILED
  See error report: rsb-report-expat-2.1.0-x86_64-w64-mingw32-1.txt
error: building e2xwm1
Build Set: Time 0:14:13.561418
Build FAILED

The following is the content of  
rsb-report-expat-2.1.0-x86_64-w64-mingw32-1.txt:

 RTEMS Tools Project - Source Builder Error Rep

Re: malloc info

[Chris Johns]

On 09/02/2018 00:59, Mikhail Svetkin wrote:
> Hi all, 
> 
> I am trying to investigate memory leak in my application.
> 
> I check malloc information via malloc_free_space
> and rtems_shell_main_malloc_info and i see after some times that they have
> different results.
> 
> For example:
> rtems_shell_main_malloc_info prints 2mb and malloc_free_space prints 1mb
> 
> Which function should i use?
> 

There is a malloc shell command if you have the shell working or you could call
the shell command directly:

[/] # malloc
C Program Heap and RTEMS Workspace are the same.
Number of free blocks: 298
Largest free block:  160667680
Total bytes free:160971752
Number of used blocks:6707
Largest used block:   33554440
Total bytes used: 97291328
Size of the allocatable area in bytes:   258263080
Minimum free size ever in bytes: 160926264
Maximum number of free blocks ever:314
Maximum number of blocks searched ever: 90
Lifetime number of bytes allocated: 1116295560
Lifetime number of bytes freed: 1019006776
Total number of searches: 28918650
Total number of successful allocations:   28446143
Total number of failed allocations:  0
Total number of successful frees: 28439436
Total number of successful resizes:120

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

RTEMS Open Class in Huntsville AL US April 23-27

[Joel Sherrill]

Hi

There will be an RTEMS Open Class in Huntsville Alabama the
week of April 23-27.

April 23 - Getting Started
April 24 - 27 - Open Class

Details and registration forms at http://rtems.com/trainingschedule.

If you have questions at all about the class, feel free to email me directly.

Thanks.


--joel
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

malloc info

[Mikhail Svetkin]

Hi all,

I am trying to investigate memory leak in my application.

I check malloc information via malloc_free_space
and rtems_shell_main_malloc_info and i see after some times that they have
different results.

For example:
rtems_shell_main_malloc_info prints 2mb and malloc_free_space prints 1mb

Which function should i use?


Best regards,
Mikhail
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users