Re: Compilation error in libpci path inclusion.
AFAIK unless someone has added some support, the drvmgr was written by the Gaisler folks for SPARC BSPs and that's all the BSPs that work with it so far. --joel On Feb 14, 2017 11:46 PM, "John Soni Jose" wrote: > Hi All, > > Any inputs or suggestions to move forward on this issue. > > Regards > > John > > > On Tuesday 14 February 2017 03:46 PM, John Soni Jose wrote: > >> Hi All, >> >> Trying to execute PCI shell terminal task "cpukit/libmisc/shell/main_pci" >> on an x86 machine. >> >> Made below changes for including LIBPCI. The changes were made in "cpukit/ >> configure.ac" and "cpukit/libmisc/shell/shellconfig.c" >> >> diff --git a/cpukit/configure.ac b/cpukit/configure.ac >> index 3d6888c..095866e 100644 >> --- a/cpukit/configure.ac >> +++ b/cpukit/configure.ac >> @@ -385,7 +385,7 @@ AC_MSG_RESULT([$HAVE_SHA]) >> # Filter libpci to only build for architectures that have support for it >> AC_MSG_CHECKING([whether CPU supports libpci]) >> case $RTEMS_CPU in >> - sparc) >> + sparc | i386) >> HAVE_LIBPCI=yes ;; >>*) >> HAVE_LIBPCI=no ;; >> >> diff --git a/cpukit/libmisc/shell/shellconfig.c >> b/cpukit/libmisc/shell/shellconfig.c >> index 11a4ff0..a676550 100644 >> --- a/cpukit/libmisc/shell/shellconfig.c >> +++ b/cpukit/libmisc/shell/shellconfig.c >> @@ -15,5 +15,6 @@ >> >> #define CONFIGURE_SHELL_COMMANDS_INIT >> #define CONFIGURE_SHELL_COMMANDS_ALL >> +#define RTEMS_PCI_CONFIG_LIB >> >> diff --git a/cpukit/libpci/Makefile.am b/cpukit/libpci/Makefile.am >> index cf336ed..a0dff03 100644 >> --- a/cpukit/libpci/Makefile.am >> +++ b/cpukit/libpci/Makefile.am >> @@ -41,7 +41,7 @@ libpci_a_SOURCES += pci_print.c >> # Driver manager PCI bus >> libpci_a_SOURCES += pci_bus.c >> include_drvmgrdir = $(includedir)/drvmgr >> -include_drvmgr_HEADERS = pci_bus.h >> +include_drvmgr_HEADERS = pci_bus.h drvmgr.h >> >> After the above changes ran bootstrap command to regenerate preinstall.am >> files. >> >> Hitting this compilation error. The same error is happening for both x86 >> and leon2 >> >> "gmake[6]: *** No rule to make target `drvmgr.h', needed by >> `../../cpukit/../../../pc386/lib/include/drvmgr/drvmgr.h'. Stop. >> gmake[6]: Leaving directory `/opt/RTEMS/sandbox/i386-rtems >> 4.12/i386-rtems4.12/c/pc386/cpukit/libpci'" >> >> "gmake[6]: Entering directory `/opt/RTEMS/sandbox/leon-rtems >> 4.12/sparc-rtems4.12/c/leon2/cpukit/libpci' >> gmake[6]: *** No rule to make target `drvmgr.h', needed by >> `../../cpukit/../../../leon2/lib/include/drvmgr/drvmgr.h'. Stop." >> >> >> Do we need to enable any other flags for successful compilation of libpci >> ? >> >> Regards >> >> John >> >> >> >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel >> >> > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH 8/9] Patching USB serial drivers and Termios for use in RTEMS
On Tue, Feb 14, 2017 at 9:43 PM, Chris Johns wrote: > On 15/02/2017 00:33, Sebastian Huber wrote: >> >> For imports of FreeBSD files into RTEMS or Newlib, please use the SVN >> checkout to get the right $FreeBSD$ identifiers, e.g. >> >> >> https://git.rtems.org/rtems/tree/cpukit/libcsupport/include/sys/event.h#n26 >> > > Maybe a note in libbsd about this would help? I no idea where else this > could be documented. > For RTEMS proper we keep this kind of information somewhere in our coding conventions, currrently these are documented on our wiki. In this case, a line item can be added to Maintainability, or to the linked 3rd party code to call out FreeBSD code specifically. https://devel.rtems.org/wiki/Developer/Coding/Conventions#Maintainability https://devel.rtems.org/wiki/Developer/Coding/ThirdPartyCode > Chris > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: qemu RSB bset with gcc 6.3.0
On Feb 14, 2017 8:47 PM, "Chris Johns" wrote: On 15/02/2017 04:00, Joel Sherrill wrote: > Hi > > Helping someone using Debian unstable which uses gcc 6.3.0. glib has > code using strftime() which is now flagged and glib is compiled with > -Werror. > > gdate.c:2497 in glib 2.39. On the glib master at github, it is line 2500 > and > the code is fixed with a blame/comment in 2002. > > My first thought was to bump the glib version but glib is at 2.50 and > I am concerned about interface changes. Besides, this isn't fixed > on their master from what we saw. > > Someone reported this to Freedesktop with this issue: > > https://bugs.freedesktop.org/show_bug.cgi?id=95326 > > Any thoughts? > > I have some patches sitting around somewhere to bump a few bits and pieces used to build qemu when I tried to build qemu on OSX. I could not get it to build and I did not have the time to complete the work. I filed a ticket and think I have the solution based on that ticket. Just need to spend the time updating the package. I don't see any reason to investigate rebaselining qemu yet. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: qemu RSB bset with gcc 6.3.0
Hi again, I am taking a shot at fixing this and fetching the patches from the Freedesktop ticket. https://bugs.freedesktop.org/show_bug.cgi?id=95326 When I use wget to fetch the patch link, the file names are of the form: gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7 52ecda6335add96494a178186bf7d490 And the RSB is fetching both as "gdate.c" How do I fetch these patches and specify the md5 sum? %patch add glib https://git.gnome.org/browse/glib/patch/glib/gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7 %hash md5 gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7 52ecda6335add96494a178186bf7d490 %patch add glib https://git.gnome.org/browse/glib/patch/glib/gdate.c?id=8cdbc7fb2c8c876902e457abe46ee18a0b134486 %hash md5 gdate.c?id=8cdbc7fb2c8c876902e457abe46ee18a0b134486 16bc0b96bbfa7c2b350df6f4aff2db29 Thanks. --joel On Wed, Feb 15, 2017 at 7:10 AM, Joel Sherrill wrote: > > > On Feb 14, 2017 8:47 PM, "Chris Johns" wrote: > > On 15/02/2017 04:00, Joel Sherrill wrote: > >> Hi >> >> Helping someone using Debian unstable which uses gcc 6.3.0. glib has >> code using strftime() which is now flagged and glib is compiled with >> -Werror. >> >> gdate.c:2497 in glib 2.39. On the glib master at github, it is line 2500 >> and >> the code is fixed with a blame/comment in 2002. >> >> My first thought was to bump the glib version but glib is at 2.50 and >> I am concerned about interface changes. Besides, this isn't fixed >> on their master from what we saw. >> >> Someone reported this to Freedesktop with this issue: >> >> https://bugs.freedesktop.org/show_bug.cgi?id=95326 >> >> Any thoughts? >> >> > I have some patches sitting around somewhere to bump a few bits and pieces > used to build qemu when I tried to build qemu on OSX. I could not get it to > build and I did not have the time to complete the work. > > > I filed a ticket and think I have the solution based on that ticket. Just > need to spend the time updating the package. > > I don't see any reason to investigate rebaselining qemu yet. > > > Chris > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
