gcc-python-plugin March 2013

gcc-python-plugin@lists.stg.fedorahosted.org

4 participants
4 discussions

Plenty of tests failing with python 2.7.3 and gcc 4.7.2
by Matej Cepl 20 Mar '13

20 Mar '13

I have just tried running make with the fresh clone of gcc-python-plugin (commit 537bbc9) and the results of tests were not completely satisfactory to say it mildly (see http://mcepl.fedorapeople.org/tmp/gcc-python-plugin-log.txt.bz2 for the log). Any thoughts? Matěj -- http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC Home is where ~/.bashrc is. -- from Usenet -- http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC To err is human, to purr feline.

2 1

yelp visualization code
by Buck Golemon 18 Mar '13

18 Mar '13

David: You have permission to re-license that code under GPL2 or MIT, or whatever you choose. Actually, I guess this effectively puts it under the WTFPL..

1 0

man Target Gone
by David Narvaez 06 Mar '13

06 Mar '13

Hi, I see that commit 233920649d310a0210e37b2845b77b2c8a531046 dropped the man target, is that intentional? David E. Narváez

2 1

We now have a "make install" target
by David Malcolm 01 Mar '13

01 Mar '13

I've implemented a "make install" target in the Makefile, based on what was in the rpm specfile. This is slightly complicated by the fact we now have the gcc-c-api layer. This builds as gcc-c-api/libgcccapi.so which the plugin links against. So when running the plugin from a working copy, use LD_LIBARY_PATH=gcc-c-api so that the plugin can find its libgccapi.so there. This is already done by the Makefile targets that run the plugin, via INVOCATION_ENV_VARS := LD_LIBRARY_PATH=gcc-c-api When installing, both the plugin and libgccapi.so will be installed to GCC's plugins directory (e.g /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/plugin/ on this machine) so we give the plugin an RPATH that points at that directory so that it finds the libgcccapi.so there (to support the case of having multiple GCCs installed). Ultimately I hope to move gcc-c-api out from the plugin's source tree and into its own project once it's proven itself, but the above approach seems to me to be a good way forward in the meantime. I'm working on getting the plugin to work fully with GCC 4.8 (or at least the build from SVN I have on my machine) and hope to do a new release soon, so please let me know if I broke anyone's builds of the plugin in the above! Cheers Dave

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

gcc-python-plugin March 2013