-
Notifications
You must be signed in to change notification settings - Fork 29
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
RFE: Handle LIBRARY_PATH #121
Comments
What do you mean by handled correctly? LIBRARY_PATH is used by gcc in native configurations, which is backwards from what you're describing and also requires no special handling on the part of perl-cross. The correct handling is to leave it in the environment, unchanged. I've never heard of HOSTLIBRARY_PATH and neither has Google apparently. |
I'm talking about this section here, where special perl-cross/cnf/configure_tool.sh Lines 171 to 187 in 1a0ca3b
|
Ok, and what should configure do about these variables in your opinion? To clarify, I have a rough idea of what you're trying to do, but I don't understand what exactly you want changed in perl-cross specifically and why doing that would be a good idea. |
My idea is basically this: When you do normal builds, you set In the same line of reasoning, for a normal build you could be using So in order to have perl-cross continue along the principle of "just do what you do for a native build and perl-cross will sort everything out for a cross build", I think the following needs to be added:
|
There might be more to it though, I haven't dug that deep in to perl-cross. These variables need to have the above behaviour as |
In our build system we sometimes use
$LIBRARY_PATH
rather than$LDFLAGS
to control where the compiler searches for libraries. It would be a nice future feature if that variable could also be handled correctly, i.e. a separate$LIBRARY_PATH
and$HOSTLIBRARY_PATH
.The text was updated successfully, but these errors were encountered: