[Cynede]

Re-created: #9760

Now, without adding pc-linux-gnu platform

Re-created: #9565

t will be useful for unix systems, some package managers and external tools that is passing / maybe looking for GNU configure syntax options.

One of related bugs: #5138

Also that could be useful in future if project will really install man pages / other stuff using those variables.

[brson]

Thanks again @Heather 🎆

[brson]

@Heather no, I'm not sure about changing unknown to pc, but I'm worried about assumptions that some of our automation might be making about the names of the triples. I'd rather just do these things separately to be safe.

[brson]

Er, that last comment should have been on #9760

[Cynede]

@brson well I can do it but I guess /usr/share/man should be $CFG_PREFIX/usr/share/man and not $CFG_PREFIX/man

[brson]

@Heather Maybe $CFG_PREFIX/share/man since $CFG_PREFIX is likely to equal /usr/local, putting the man pages at /usr/local/share/man.

Here are my best guesses for all the default values:

valopt localstatedir "/var/lib" "local state directory"
valopt sysconfdir "/etc" "install system configuration files"
valopt datadir "$CFG_PREFIX/share" "install data"
valopt infodir "$CFG_PREFIX/share/info" "install additional info"
valopt mandir "$CFG_PREFIX/share/man" "install man pages in PATH"
valopt libdir "$CFG_PREFIX/lib" "install libraries" 

Presumably /var/lib and /etc don't use the prefix.

[Cynede]

@bors it's wrong in my opinion, everything should use prefix to allow sandboxed build and installation.

[thestinger]

DESTDIR is for setting the top-level installation directory, and is the convention used by almost every open-source project with a Makefile. The standard line in a package script is either ./configure --prefix=/usr && make DESTDIR="$pkgdir" or make PREFIX=/usr DESTDIR="$pkgdir".

[Cynede]

@thestinger ah, right. I'm wrong there. Will use @brson solution then.

[Cynede]

@brson added correction

[Cynede]

@brson failed to build? where can I see exact log?

[brson]

@Heather the links in bors' output link to the log files. It appears that those links disappeared when you rebased and repushed. I r+ed again so let's see what happens this time.

[Cynede]

@brson IOError: [Errno 2] No such file or directory: 'x86_64-unknown-linux-gnu/stage0/lib/libstd-6c65cf4b443341b1-0.9-pre.so' ?

[brson]

@Heather I still don't understand that error on the bots, but I did some tests locally and discovered I needed the following diff in order for all the triple variables to be set up correctly. This does the conversion from the old _TRIPLES variables to the new before the new variables are used in various calculations, reproduces some logic for assigning the target triples, and also fixes a typo.

diff --git a/configure b/configure
index 0f965fc..d8b28bb 100755
--- a/configure
+++ b/configure
@@ -616,6 +616,26 @@ do
 done
 CFG_TARGET=$V_TEMP

+# copy host-triples to target-triples so that hosts are a subset of targets
+# XXX: remove deprecated variables here
+V_TEMP=""
+for i in $CFG_HOST_TRIPLES $CFG_TARGET_TRIPLES;
+do
+   echo "$V_TEMP" | grep -qF $i || V_TEMP="$V_TEMP${V_TEMP:+ }$i"
+done
+CFG_TARGET_TRIPLES=$V_TEMP
+
+# XXX: Support for deprecated syntax, should be dropped.
+if [ ! -z "$CFG_BUILD_TRIPLE" ]; then
+    CFG_BUILD=${CFG_BUILD_TRIPLE}
+fi
+if [ ! -z "$CFG_HOST_TRIPLES" ]; then
+    CFG_HOST=${CFG_HOST_TRIPLES}
+fi
+if [ ! -z "$CFG_TARGET_TRIPLES" ]; then
+    CFG_TARGET=${CFG_TARGET_TRIPLES}
+fi
+
 # check target-specific tool-chains
 for i in $CFG_TARGET
 do
@@ -718,7 +738,7 @@ then
     CFG_LIBDIR=bin
 fi

-for h in $CFG_HOST_
+for h in $CFG_HOST
 do
     for t in $CFG_TARGET
     do
@@ -986,20 +1006,6 @@ putvar CFG_ANDROID_CROSS_PATH
 putvar CFG_MINGW32_CROSS_PATH
 putvar CFG_MANDIR

-# Support for deprecated syntax, should be dropped.
-putvar CFG_BUILD_TRIPLE
-putvar CFG_HOST_TRIPLES
-putvar CFG_TARGET_TRIPLES
-if [ ! -z "$CFG_BUILD_TRIPLE" ]; then
-    CFG_BUILD=${CFG_BUILD_TRIPLE}
-fi
-if [ ! -z "$CFG_HOST_TRIPLES" ]; then
-    CFG_HOST=${CFG_HOST_TRIPLES}
-fi
-if [ ! -z "$CFG_TARGET_TRIPLES" ]; then
-    CFG_TARGET=${CFG_TARGET_TRIPLES}
-fi
-
 if [ ! -z "$CFG_ENABLE_PAX_FLAGS" ]
 then
     putvar CFG_ENABLE_PAX_FLAGS

[Cynede]

@brson thanks, added this patch.

[Cynede]

• re-based commits another time

[Cynede]

@brson -m32: command not found ?

[Cynede]

Hello... May someone help me to understand what is happening here? Should I rebase my branch now?

[brson]

@Heather I'll try a build on windows and see if I can figure out what's wrong.

[brson]

I can't reproduce this failure. I do see the strange errors about -m32 command not found but they don't appear to be fatal. Can you rebase?

[Cynede]

@brson rebased

[brson]

I don't want to keep asking for rebases so I rebased and reopened as #10164