public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gonçalo Antunes" <gmma@gmma.net>
To: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] i386 problem
Date: Sat, 30 Apr 2005 09:57:00 -0000	[thread overview]
Message-ID: <001d01c54d35$4b9e05e0$0200a8c0@pcgoncalo> (raw)
In-Reply-To: <20050427053432.GY17364@lunn.ch>

Hello again!

I tried to start with a plain net template, changed the HAL_STARTUP to 
FLOPPY and the error on the "make tests" is the same:

>>/home/gmma/config_install/lib/vectors.o:/tmp/ccfRQjJM.s: undefined 
>>reference
>> to 'hal_saved_interrupt_state'
>> make: leaving directory '/home/gmma/config_build'
>> collect2: ld returned 1 exit status


If I put it to RAM, it works fine...

When I first installed ecos (without any CVS update), the FLOPPY startup 
worked fine...

What can I do?


Thank You very much.


----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Gon?alo Antunes" <gmma@gmma.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, April 27, 2005 6:34 AM
Subject: Re: [ECOS] i386 problem


> On Wed, Apr 27, 2005 at 01:20:52AM +0100, Gon?alo Antunes wrote:
>> Hi
>>
>> I started my config.ecc with the i386realtek template.
>> added the HTTP, CPuload, FreeBSD, networking, and common ethernet 
>> packages..
>
> Use the net template as a basis and then add http and cpuload.
>
> This might help, but it might not.
>
>> and when I do the 'make tests" I get an error...
>>
>> I'm using the startup method 'FLOPPY' and I get the following error:
>>
>> /home/gmma/config_install/lib/vectors.o:/tmp/ccfRQjJM.s: undefined 
>> reference
>> to 'hal_saved_interrupt_state'
>> make: leaving directory '/home/gmma/config_build'
>> collect2: ld returned 1 exit status
>>
>> if  I  change the startup method to RAM, the error does not appear...
>> I really need to have it running from the FLOPPY...
>
> What have you found out while debugging the problem? Its been a few
> days since you posted this the first time so you have had time to do
> lots of testing....
>
>        Andrew
> 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-04-30  3:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050426204513.30E1BE5BC7@ws7-2.us4.outblaze.com>
2005-04-27  0:21 ` [ECOS] RE: eCos Loader David Bonfrer
2005-04-27  0:33   ` [ECOS] i386 problem Gonçalo Antunes
2005-04-27  6:05     ` Andrew Lunn
2005-04-30  9:57       ` Gonçalo Antunes [this message]
     [not found]         ` <20050430171810.GA6601@lunn.ch>
2005-05-02 16:12           ` Gonçalo Antunes
2005-05-02 16:30             ` Andrew Lunn
2005-05-02 16:35               ` Gonçalo Antunes
2005-05-03 10:14         ` Nick Garnett
2005-05-03 10:37           ` Gonçalo Antunes
2005-05-03 20:30           ` Bart Veer
2005-04-27  8:25   ` [ECOS] RE: eCos Loader Andrew Lunn
2005-04-27 10:28   ` Nick Garnett
2005-04-27 18:06     ` Paul D. DeRocco
2005-04-28 10:06       ` Nick Garnett
2002-05-02  9:04 [ECOS] i386 problem Roland Caßebohm
2002-05-14 14: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='001d01c54d35$4b9e05e0$0200a8c0@pcgoncalo' \
    --to=gmma@gmma.net \
    --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).