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 > openocd.x86_64: E: missing-PT_GNU_STACK-section > /usr/lib64/openocd/ecos/at91eb40a.elf > 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 > openocd.x86_64: W: file-not-utf8 /usr/share/info/openocd.info.gz > > I need to know what they are for so I can take the appropriate action to > fix them for the RPM build for Fedora. I know the last one is the info > file. I'm going to look into making a match that makes it UTF to make > things happy. I'm not sure what the other files are for. Do they make > sense in a final distribution of OpenOCD? If so, what are they for? I > appreciate any help I can get. Thanks. > > // Dean Glazeski > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > I think :
The libddc files are for building target dcc implementations, and nothing in this list is used by the actual running openocd image on fedora. So this is really reference materials for developers. That might help you decide where to place them. Best regards, Magnus _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
