Re: absolute paths are relative to MSYS?
JonY <[email protected]> Tue, 12 Jul 2011 11:14:50 +0800
| Newsgroups | gmane.comp.gnu.mingw.msys |
|---|---|
| Message-ID | <[email protected]> |
On 7/12/2011 04:29, George Brink wrote: > I just installed the new copy of MSYS using mingw-get: > mingw-get install msys > It worked fine, but instead of the root MinGW folder it created a new one: > C:\MinGW\msys\1.0\ > and put everything there... > Ok, I can have two records in my PATH: > PATH=C:\MinGW\bin;C:\MinGW\msys\1.0\bin;%PATH% > > But now I like to compile and install some libraries. I go into the > library folder, run: > bash configure --prefix=/mingw > mingw32-make && mingw32-make install Try using "make" instead of "mingw32-make", the 2 programs are different, with the former understanding MSYS type paths that you will get from running configure shell scripts. The latter is closer to MSVC nmake where you can use win32 paths. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Mingw-msys mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-msys
0xED74C077.asc
(application/pgp-keys, 1.6 KB)
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.17 (MingW32) mQGiBEoX6mARBACDkWLtpoOo/ZGtzDJBx1Q7+/np5ILeJJVwsXsBmBnqslmzfOMA G8u1AqjBgGaY5PFlTHF4hXKfq1Y9c5EDJYLIG0Et9EE7CpOBpGqAL9HrrudErCyZ Gc4/iJuvIhWldhsNmpsuXch69fsM3Vh2OstGhO90WQGkZ5drmOZEowxSBwCglPps Cfte3WYQa1tmhnQOSR2cYbMD/Ri4mqOn21Y2X2V3/3HE0Lk6f6a9Azp4BiD5+dJv 3d5vvYEf2/oPlY8Q0xx2Mp1bULRdN1HKIVLtqrRzAdOtE4m31W2xQEIbFYk9ij7x YDBoOGam3iQ/nz9X/pka7fWIr/pdyIOZmx9a+hc2jehdOUfQNX4o0j+eMJ1DVRXQ TeJLA/4v3fhLb7HYI6hv0h0RZKRzWxnqQs9JtOWvvgC/lg/A4M3+MLkZ5NBrGiJI Eu889x+um9FNuuttO0m4G+ADt9r8oWlUrX7pMq+Z5f9stl9tITSmV07CGQeb/dse X3R/pZmxj0bQP8UJ4XEdgAs7sFNuG43eTGO6fJqvOVn5EIvPhbQjam9uX3kgPGpv bl95QHVzZXJzLnNvdXJjZWZvcmdlLm5ldD6IYAQTEQIAIAUCShfqYAIbAwYLCQgH AwIEFQIIAwQWAgMBAh4BAheAAAoJEKeegCntdMB3q4MAn3r9hhW6BHQOqkDzd7hS G4qCzVvzAJ9auqMimmrdJznw9WadoZRoup1iZrkCDQRKF+pgEAgAykLcD/2U6vck 4l+E6Uyv4S7UuqXG/+KWz7CLZo4Pez/7k+32HLKwMvmlwoLc9YOM9LaPGjOR4xPN eVH6kFkd+p0DXy5bSEpbO/ZXFGSA+PwJD/uITIu2kKv4tNh1YwaIgdnxUxaw6dVv fvmG45hNGetZBVARrT3G7XT9MAEDjaEuXJVwJbD16bjKw88sK2s/DNVFGsnYcrUL EM2dtCMtCrV6c0jLWe5oatfrYwT5HX0nA57Xnnwz4Ipe0vUSnl/wrbwhqQCnYLlm apVu+P9DBvBRZ0YzgsIJNu5QKJE2aeoRDMP5gdm+YlIhG3PEaKGXPGuNXqwrnICR Up63C6Ss6wADBgf/XMg955hahDrjDZ2aZuf2IxkafCZk1HIxl1UcilJ8dOgSeBmC /h1Uqxbe0ibzsgg2n/r+oMvU510vnvhcCAUdRiWYBluN7VPzKGo9megwhZpnGXcI 7WweogiwdFxwP5mqqTYpmL1Qc6NdRewE3VAEoOO2fQkJicAoO2zfhEtx1JL1DTwY Y1TDOriihOs2FX1zPUn8T0hSTPQwGP108ZNOSYeE3zSNko0uOMHwmn4A6R5ZQW9k GX+EiTOm9zBqMhZgHHeFkme/rPXHagh/MG8PiIWVBYucUWDe5DUb6TV4r7dKLZFS 0o0uWSMHo1hQeyBuGXJPpRZERMoDXcUVMnAd0YhJBBgRAgAJBQJKF+pgAhsMAAoJ EKeegCntdMB3OQYAnjvSniU2qAHp4dkKZCOl1xLgKy9nAJ9JXl+cxyjgsuPaVU1q O0yvIxAf/Q== =a1qp -----END PGP PUBLIC KEY BLOCK-----
signature.asc
(application/pgp-signature, 196 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iEYEARECAAYFAk4bvC4ACgkQp56AKe10wHensQCfUSZtt+uHwoz0JeiOP4FFfOCY MG8AnjZx1L7LiaqsquT1ofCc1C+i+j6k =mhll -----END PGP SIGNATURE-----