Duane Ellis wrote:
Dean Glazeski wrote:
Hey all,

Can anyone give me insight on these files:

openocd.x86_64: E: statically-linked-binary /usr/lib64/openocd/ecos/at91eb40a.elf
/usr/lib64/openocd/ecos/at91eb40a.elf
These are *TARGET* files, the "package tool" you have is *WRONG*HEADED*, or mis-informed - it sees the file as an ELF, then wrong assumes it is an *ELF* target for the intended HOST. You might want to ask the packaging people how to identify such files My hunch is, they have *NEVER* thought about this situation!
The interesting thing about this is that Fedora is sort of hard set on following a filesystem hierarchy standard <http://www.pathname.com/fhs/>. What this basically means is that architecture specific files go into lib while architecture independent files belong in share. This means that all of the target scripts and this elf file should probably be installed into /usr/share/. I can use patches to fix this for the Fedora RPM if you can tell me how to tweak the build so that the files go elsewhere :). It might be good to consider fixing this to follow the FHS in the current head.

openocd.x86_64: W: devel-file-in-non-devel-package /usr/share/openocd/contrib/libdcc/example.c openocd.x86_64: W: devel-file-in-non-devel-package /usr/share/openocd/contrib/libdcc/dcc_stdio.c openocd.x86_64: W: devel-file-in-non-devel-package /usr/share/openocd/contrib/libdcc/dcc_stdio.h

Again, I think the "package tool is wrong" or mis-informed, this is a "cross compilation package" - these are example source files that a user of this tool might use - they are not *HOST* files, but are instead, *TARGET* files and are rightfully included in the package.
Yeah, I don't know how to fix this one. It goes to the right area according to FHS, but it's being picked up as problematic (really just a warning). I'm searching around wiki pages, google, and IRC chats for answers.
openocd.x86_64: W: file-not-utf8 /usr/share/info/openocd.info.gz



This I don't know enough about TexInfo stuff to answer - sorry.

-Duane.

Thanks for the responses.

// Dean Glazeski
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to