From: "Thomas Höhenleitner" <ecos@seerose.net>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ecosadmin warning: 2 packages missing
Date: Fri, 23 Jun 2006 12:31:00 -0000 [thread overview]
Message-ID: <j1bc4z.zdz4an@www.seerose.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hello,
right now (ok, a few minute ago) I checked out the latest CVS version
and performed the following command:
export ECOS_REPOSITORY=/opt/ecos/eCosCVS/ecos/packages &&
/opt/ecos/eCosCVS/ecos/packages/ecosadmin.tcl list 2> emsg | head > msg
In msg I get:
ecosadmin warning: package CYGPKG_IO_USB_SLAVE_TTY at
/opt/ecos/eCosCVS/ecos/packages/io/usb/tty/slave missing
ecosadmin warning: package CYGPKG_DEVS_ETH_ARM_AT91 at
/opt/ecos/eCosCVS/ecos/packages/devs/eth/arm/at91 missing
CYGPKG_HAL: current
CYGPKG_INFRA: current
CYGPKG_IO: current
CYGPKG_IO_SERIAL: current
CYGPKG_IO_CAN: current
CYGPKG_DEVS_CAN_MCF52xx_FLEXCAN: current
CYGPKG_IO_CAN_LOOP: current
CYGPKG_IO_PCMCIA: current
My gentle question: Is there s.th. inconsistent in the repository?
Following just for information (probably of different matter).
In emsg I see:
error writing "stdout": broken pipe
while executing
"puts "ecosadmin error: $error_message""
invoked from within
"if { ! [info exists ecosadmin_not_standalone] } {
# Decide where warnings and fatal errors should go.
ecosadmin::initialise_error_handling
# Firs..."
(file "/opt/ecos/eCosCVS/ecos/packages/ecosadmin.tcl" line 1321)
This is occurs only in connection with the head command.
Thomas
[-- Attachment #2: cmd --]
[-- Type: text/plain, Size: 130 bytes --]
export ECOS_REPOSITORY=/opt/ecos/eCosCVS/ecos/packages && /opt/ecos/eCosCVS/ecos/packages/ecosadmin.tcl list 2> emsg | head > msg
[-- Attachment #3: emsg --]
[-- Type: text/plain, Size: 346 bytes --]
error writing "stdout": broken pipe
while executing
"puts "ecosadmin error: $error_message""
invoked from within
"if { ! [info exists ecosadmin_not_standalone] } {
# Decide where warnings and fatal errors should go.
ecosadmin::initialise_error_handling
# Firs..."
(file "/opt/ecos/eCosCVS/ecos/packages/ecosadmin.tcl" line 1321)
[-- Attachment #4: msg --]
[-- Type: text/plain, Size: 429 bytes --]
ecosadmin warning: package CYGPKG_IO_USB_SLAVE_TTY at /opt/ecos/eCosCVS/ecos/packages/io/usb/tty/slave missing
ecosadmin warning: package CYGPKG_DEVS_ETH_ARM_AT91 at /opt/ecos/eCosCVS/ecos/packages/devs/eth/arm/at91 missing
CYGPKG_HAL: current
CYGPKG_INFRA: current
CYGPKG_IO: current
CYGPKG_IO_SERIAL: current
CYGPKG_IO_CAN: current
CYGPKG_DEVS_CAN_MCF52xx_FLEXCAN: current
CYGPKG_IO_CAN_LOOP: current
CYGPKG_IO_PCMCIA: current
[-- Attachment #5: Type: text/plain, Size: 148 bytes --]
--
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:[~2006-06-23 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=j1bc4z.zdz4an@www.seerose.net \
--to=ecos@seerose.net \
--cc=ecos-discuss@ecos.sourceware.org \
/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).