Hi Eric,
thanks for pursuing this.
* Eric Blake wrote on Wed, May 13, 2009 at 02:51:34PM CEST:
> @@ -156,7 +158,25 @@ Installation Names
> In addition, if you use an unusual directory layout you can give options
> like @option{--bind...@var{dir}} to specify different values for
> particular ki
>+Depending on the package, the default directory layout chosen during
>+...@command{configure} can be altered during subsequent execution of
>+...@command{make}.
>
> A `make install FOO=VAL' should never alter anything in the build
> directory. The problem is if y
לכולנו לפתוח את הלב לשאת תפילה ולעזור,
סיון שלח/ה לך תוכן מאתר mako שהוא חושב שיעניין אותך.
לצפייה בתוכן, אנא הקלק על
http://www.mako.co.il/tv-ilana_dayan/2009-b456ae2c64031210/Article-dd9fb305b853121006.htm
אשחר כולנו מאחלים לך החלמה מהירה שתתרפא במהרה כדרך נס כאילו המחלה מעולם לא
הייתה
בברכה,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alfred M. Szmidt on 5/13/2009 7:22 AM:
>+Depending on the package, the default directory layout chosen during
>+...@command{configure} can be altered during subsequent execution of
>+...@command{make}.
>
> A `make install FO
+Depending on the package, the default directory layout chosen during
+...@command{configure} can be altered during subsequent execution of
+...@command{make}.
A `make install FOO=VAL' should never alter anything in the build
directory. The problem is if you pass --bindir=/foo to confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 4/15/2009 5:51 AM:
>> Maybe the generic INSTALL file should provide pointers to more
>> comprehensive documentation?
>
> I tend to agree that INSTALL should either mention DESTDIR (and probably
> also V, which now plays a ro
