public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ron Kundla <rkundla@nband.com>
To: "eCos Mailing List (E-mail)" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Build error under current x86 - have you seen this?
Date: Tue, 24 Jul 2001 17:20:00 -0000	[thread overview]
Message-ID: <C91EB7099291D3118E7600A0C9E91B297B52E6@gonband.nband.com> (raw)

Hello!

I have had a nagging problem for some time and haven't quite identified
where the root of this problem is located.

I am building from the current eCos build (taken from CVS) and when I select
the template for networking on the x86 platform, I am able to build the
library with no problems but get an error during building the tests

i386-elf-gcc -c  -I//C/cygwin/eCos/build/x86/net_install/include
-I//C/cygwin/eCos/src/ecos/packages/io/fileio/current
-I//C/cygwin/os/src/ecos/packages/io/fileio/current
-I//C/cygwin/eCos/src/ecos/packages/io/fileio/current/src
-I//C/cygwin/eCos/src/ecos/packages/io/fileio/current/tests -I.
-I//C/cygwin/eCos/src/e
-I//C/cygwin/eCos/src/ecos/packages/io/fileio/current/tests/ -Wall
-Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woith
-Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -Wp,-MD,tests/stdio.tmp -o
tests/stdio.o
//C/cygwin/eCos/src/ecos/packages/io/fileeio/current/tests/stdio.c
In file included from
//C/cygwin/eCos/src/ecos/packages/io/fileio/current/tests/stdio.c:61:
//C/cygwin/eCos/src/ecos/packages/io/filestdio.c:61:
//C/cygwin/eCos/src/ecos/packages/io/fileio/current/tests/testfs.c:190:
warning: alig90: warning: alignment of `testfs_fste' is greater than maximum
object file alignment. Using 4.
//C/cygwin/nment. Using 4.
//C/cygwin/eCos/src/ecos/packages/io/fileio/current/tests/testfs.c:20.c:206:
warning: alignment of `testfs_mte1' is greater than maximum object file
alignment. Using 4.
i386-elf-gcc -g -nostdlib -Wl,-i386-elf-gcc -g -nostdlib -Wl,--gc-sections
-Wl,-static -L//C/cygwin/eCos/build/x86/net_install/lib -Ttarget.ld -o
//C/cygwin/eCos/bux86/net_install/lib -Ttarget.ld -o
//C/cygwin/eCos/build/x86/net_install/tests/io/fileio/current/tests/stdio
tests/stdio.o
//C///C/cygwin/eCos/build/x86/net_install/lib/libtarget.a(language_c_libc_st
dio_fopen.o): In function `fdopen':
//C/cygwin/eCosn.o): In function `fdopen':
//C/cygwin/eCos/build/x86/net_install/include/cyg/libc/stdio/stream.inl:434:
undefined reference to `__builtin_new'
collect2: ld returned 1 exit status
make[1]: ***
[//C/cygwin/eCos/build/x86/net_install/tests/io/fileio/fileio/current/tests/
stdio] Error 1
make[1]: Leaving directory `/eCos/build/x86/net_build/io/fileio/current'
make: *** [tests] Error 2

The part I am concerned about is the undefined reference to '__builtin_new'
from the stream.inl file. I have looked at fdopen and there is a call to a
C++ function that does a 'set_position', which coincides with the above
error.

I have checked the eCos configuration and I do have FILEIO enabled and the
macro is defined.

Any ideas?

Thanks,
Ron Kundla
nBand Communications, Inc.

             reply	other threads:[~2001-07-24 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 17:20 Ron Kundla [this message]
2001-07-24 19:22 ` Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C91EB7099291D3118E7600A0C9E91B297B52E6@gonband.nband.com \
    --to=rkundla@nband.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).