On 09/17/2014 02:26 AM, Chris Johns wrote:
The JFFS2 file system can optionally use zlib as a compressor and
if this is the only reference to zlib the application will not link.
Moving libz.a into librtemscpu.a is not a wise idea.
Adding -lz does not work because librtemscpu.a is added to the
We have now a similar problem with the new PING command:
powerpc-rtems4.11-gcc --pipe -B /opt/rtems-4.11/powerpc-rtems4.11/br_uid/lib
-specs bsp_specs -qrtems -mcpu=603e -meabi -msdata=sysv -fno-common
-mstrict-align -O2 -g -fno-keep-inline-functions -Wl,-Map,b-br_uid/app.map
b-br_uid/init.o
On 18/09/2014 11:05 pm, Ralf Corsepius wrote:
On 09/17/2014 02:26 AM, Chris Johns wrote:
The JFFS2 file system can optionally use zlib as a compressor and
if this is the only reference to zlib the application will not link.
Moving libz.a into librtemscpu.a is not a wise idea.
Why ? RTEMS is
On 17/09/14 07:51, Chris Johns wrote:
On 17/09/2014 3:30 pm, Sebastian Huber wrote:
On 17/09/14 02:26, Chris Johns wrote:
The JFFS2 file system can optionally use zlib as a compressor and
if this is the only reference to zlib the application will not link.
Adding -lz does not work because
The JFFS2 file system can optionally use zlib as a compressor and
if this is the only reference to zlib the application will not link.
Adding -lz does not work because librtemscpu.a is added to the end of
ld's command line via the bsp_specs hack and user added libraries
appear before this.
---
On 17/09/14 02:26, Chris Johns wrote:
The JFFS2 file system can optionally use zlib as a compressor and
if this is the only reference to zlib the application will not link.
Adding -lz does not work because librtemscpu.a is added to the end of
ld's command line via the bsp_specs hack and user
