<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/81235>81235</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
test-release.sh -triple doesn't set LLVM_HOST_TRIPLE
</td>
</tr>
<tr>
<th>Labels</th>
<td>
new issue
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
tstellar
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
rorth
</td>
</tr>
</table>
<pre>
When building LLVM 18.1.0 rc2 on Linux/sparc64, I passed `-triple sparcv9-unknown-linux-gnu` (overriding the `config.guess` default of `sparc64-unknown-linux-gnu` to avoid the inconsistency meant to be handled by [[Driver] Support non-canonical triples with new runtime lib layout](https://reviews.llvm.org/D133407)).
Unfortunately, the only effect of `test-release.sh -triple <triple>` is to change the triple used in the final tarball. Unexpectedly, to actually build LLVM with a different triple requires to also pass `-configure-flags "-DLLVM_HOST_TRIPLE=$triple"` which is highly unintuitive and in this case only noticed after the build has finished.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJx0k0_PnDYQxj-NuYxAYGB3OXBIslk10lu1apL2GBkz4Gn92lt7vJv99pVZ0qpVcwGE59_vmccqRlod4ij6t0JKjozWqiCkFP25UImND2PwgU0x-fkx_mbQwZTIzuRWeHn59UdoTlVT1RC0BO_ghVz6KuQlXlXQh07Id_ABripGnEEc6pIDXS3CdnwbyuT-cP7uSpvTytUlcahByJO_YQi0NWGDOVN7t9BarQljzEEzLipZBr_k073d_9djD-rmad5KkdPeRYqMTj_gFZXjHDAhGOVmizNMD8hq9G_PgW4YRH-Gj-l69YHBeVdq5bwjrSw8WSLciQ04vENIjukVwdIEVj18YtGfhTwZ5msU7RshL0JeAt4I77Gy9vZa-bAKeTk3bdvVRyEHIYdK1GdRv3k-P7vFB05OMdpHVjMzeGcfgMuC-hs_Y-QyoEUVsYoGvuks2nfPL9G-z1JQzLDaKLfiVmqPS3k_5LZfC7kMp8KkrK0APjv8ekXNOO8TeFCak7L28bTC0webCgpmWhYMmFV9lg74Z6KAW2Nlo9_csHnhudIUsFysWiMIKctzrvXlh58-fvry6ZcPP7-8F-1ZyG6HkDJD3A1pk1EMrcY-IDlynIjphqDczkERtIq7Vs4zaZxBLYxhg3wOblTMuBQNzlUxj-08tIMqcGyO9bE7DEN3LMyoD2pppGqH03CqD4dp6pfuqOf-OB2w1X1X0Chr2dWyHuqhkfJYdU1T932zdMNpahdZi67GV0X2750XFGPC8dTIti-smtDG_QpmH22H-x0MY84pp7RG0dWWIv_jnIKJLY7fW_7sMTohjwwRGf4rbJGCHf_tzJXYpKnS_lXIS26yv8pr8L-jZiEv22hRyMs2-l8BAAD__ySyajU">