-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CFLAGS build issues #287
Comments
Thanks for the
So I think the change you propose here cannot be applied. But the good thing it that the |
well, for the compat-version this is required, so if this does not satisfy, the setup is already kind of broken. however, without this fix, the prefix option is (from my point of view) is broken. it feels pretty odd/wrong to have
furthermore libdir, libexecdir,datarootdir,mandir,docdir,vimdatadir have to be manually prefix (with an alternative to facilitate compability to all (but in my eyes stranges/broken setups) would be to add a --moduleshome option with the parentdir of the initdir as default. |
To clarify a bit more: the main compability I would like to keep is for users that had a local installation (default options -> |
I am splitting this issue in two: this one regarding the CFLAGS issue reported and fixed and #292 on the MODULESHOME configuration. |
Following a typical linux layout, e.g.
will lead to a wrong and empty
MODULESHOMES
(which seems not to be used by the tool itself, but is mainly used as$MODULESHOMES/init/<init-skript>
by external scripts).Furthermore compiling with custom
CFLAGS
does not work due to space typo.Suggested patches:
The text was updated successfully, but these errors were encountered: