{"issue":{"created_at":"2011-11-30T23:16:03Z","state":"open","updated_at":"2011-12-09T19:39:13Z","comments":5,"user":{"gravatar_id":"df54b85feb7cdfd87766cf7d39475e86","id":322129,"url":"https://api.github.com/users/mandli","avatar_url":"https://secure.gravatar.com/avatar/df54b85feb7cdfd87766cf7d39475e86?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"mandli"},"body":"I am not sure if this is something we can fix but when I run any of the examples I get errors related to not including -fPIC in the compiling flags.  I ran\r\n\r\n```bash\r\nenv --unset=FFLAGS make\r\n```\r\n\r\nin one of the applications and everything worked fine.  I also tried adding\r\n\r\n```makefile\r\nifdef FFLAGS\r\n    FFLAGS += -fPIC\r\nelse\r\n    FFLAGS = -fPIC\r\nendif\r\n```\r\n\r\nto Makefile.variables which also seems to have solved the problem.  It does not look like we are doing anything special with f2py arguments so it may be prudent to either include the above Makefile fix or pass f2py the user defined FFLAGS variable through the appropriate command line flags.","assignee":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"id":2408796,"number":102,"labels":[{"name":"Bug","color":"444444","url":"https://api.github.com/repos/clawpack/pyclaw/labels/Bug"}],"title":"-fPIC not included in f2py flags when FFLAGS set","html_url":"https://github.com/clawpack/pyclaw/issues/102","closed_at":null,"url":"https://api.github.com/repos/clawpack/pyclaw/issues/102","milestone":{"created_at":"2011-05-11T08:13:17Z","state":"open","closed_issues":26,"due_on":null,"creator":{"gravatar_id":"9b677b20743558e863eca9bbd86f5d0c","id":697763,"url":"https://api.github.com/users/ketch","avatar_url":"https://secure.gravatar.com/avatar/9b677b20743558e863eca9bbd86f5d0c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"ketch"},"number":1,"description":"Fully functional 1D and 2D codes for the classic and sharpclaw routines, with all the functionality available in the Fortran codes.  We should aim to do this simultaneously with submission of a paper to SISC.","title":"PyClaw 1.0 release","url":"https://api.github.com/repos/clawpack/pyclaw/milestones/1","open_issues":10}},"action":"created","comment":{"created_at":"2011-12-09T19:39:13Z","updated_at":"2011-12-09T19:39:13Z","user":{"gravatar_id":"821b8bf222958f83097ac40befc9edd7","id":512293,"url":"https://api.github.com/users/ahmadia","avatar_url":"https://secure.gravatar.com/avatar/821b8bf222958f83097ac40befc9edd7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"ahmadia"},"body":"@mandli I'm still convinced that this is an error in your system setup, not a bug in the PyClaw build system.  Let me make sure I understand this:\r\n\r\n* If the FFLAGS environment variable exists, f2py cannot build shared objects correctly, regardless of whether you are trying to build PyClaw code or a simple Fortran module.\r\n\r\n* You can work around this by unsetting FFLAGS.  \r\n\r\nThis is because when f2py detects an exported FFLAGS it will replace its compile flags with the contents of FFLAGS, it will not append any flags that your environment fails to specify (such as building relocatable code).  The correct answer here is to either unset FFLAGS before you start trying to build PyClaw, or ensure the exported FFLAGS are correct.","id":3084377,"url":"https://api.github.com/repos/clawpack/pyclaw/issues/comments/3084377"}}