Home » Developing U++ » Releasing U++ » Tarball issues
Re: Tarball issues [message #47440 is a reply to message #47438] |
Tue, 17 January 2017 02:35 |
Sender Ghost
Messages: 301 Registered: November 2008
|
Senior Member |
|
|
amrein wrote on Mon, 16 January 2017 18:21I modified the documentation for BSD users to force them to use gmake instead of make, added some tips about this issue and reverted my patch.
'$' -> '$$' is apparently now the default substitution to use for all new gmake release (and four dollars will fail). :/
I read it in 10720 revision. But why did you use word "will" (instead of "may") in the following snippet of text?:
On BSD distributions, if you use make instead of gmake, U++ compilation will fail
For example, this is not an issue for uppsrc/umk (which also exported for current tarball), where there are no files with "$" characters for dependencies and current revision builds fine with BSD make. This is an issue for uppsrc/ide or other projects, where files with "$" character(s) may be used.
Also, I noticed about build requirements:
Build requires: gmake gtk2 freetype2 libnotify llvm39 (clang++)
Maybe this is true for some *BSD operating systems without Clang compiler in base, but Clang 3.4.1 on FreeBSD 10.3 is capable to build uppsrc/ide and uppsrc/umk projects in tarball (was tested for 10703 revision):
% which clang++
/usr/bin/clang++
% clang++ --version | head -1
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Installation of devel/llvm39 FreeBSD port is not mandatory for building of uppsrc/ide and uppsrc/umk (current revisions), at least on FreeBSD 10.3 amd64. But even if build/install it, the clang++39 (wrapper script; as part of devel/llvm39 FreeBSD port) may be used, because clang++ may be installed to different directory (which may be not exposed in (common) PATH, because other clang++ may exist in /usr/bin).
I guess, the same is possible for Clang 3.8.0 (in base) on FreeBSD 11.0.
[Updated on: Tue, 17 January 2017 07:05] Report message to a moderator
|
|
|
|
|
Tarball issues
By: mirek on Mon, 09 January 2017 09:47
|
|
|
Re: Tarball issues
By: amrein on Mon, 09 January 2017 11:22
|
|
|
Re: Tarball issues
By: amrein on Tue, 10 January 2017 19:57
|
|
|
Re: Tarball issues
By: Klugier on Tue, 10 January 2017 21:09
|
|
|
Re: Tarball issues
By: mirek on Tue, 10 January 2017 22:47
|
|
|
Re: Tarball issues
By: mirek on Tue, 10 January 2017 22:49
|
|
|
Re: Tarball issues
By: amrein on Wed, 11 January 2017 04:54
|
|
|
Re: Tarball issues
By: Klugier on Wed, 11 January 2017 13:01
|
|
|
Re: Tarball issues
By: amrein on Wed, 11 January 2017 15:15
|
|
|
Re: Tarball issues
By: Klugier on Wed, 11 January 2017 17:35
|
|
|
Re: Tarball issues
By: mirek on Wed, 11 January 2017 20:21
|
|
|
Re: Tarball issues
By: amrein on Wed, 11 January 2017 22:09
|
|
|
Re: Tarball issues
By: amrein on Wed, 11 January 2017 22:42
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: mirek on Thu, 12 January 2017 08:49
|
|
|
Re: Tarball issues
By: Tom1 on Thu, 12 January 2017 09:10
|
|
|
Re: Tarball issues
By: Tom1 on Thu, 12 January 2017 12:27
|
|
|
Re: Tarball issues
By: amrein on Thu, 12 January 2017 16:41
|
|
|
Re: Tarball issues
By: Klugier on Thu, 12 January 2017 21:17
|
|
|
Re: Tarball issues
By: amrein on Thu, 12 January 2017 23:06
|
|
|
Re: Tarball issues
By: Tom1 on Fri, 13 January 2017 10:19
|
|
|
Re: Tarball issues
By: amrein on Sat, 14 January 2017 22:18
|
|
|
Re: Tarball issues
By: amrein on Sat, 14 January 2017 22:35
|
|
|
Re: Tarball issues
By: Klugier on Sat, 14 January 2017 22:53
|
|
|
Re: Tarball issues
By: Tom1 on Sat, 14 January 2017 23:21
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 21:32
|
|
|
Re: Tarball issues
By: Klugier on Sun, 15 January 2017 22:33
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 22:59
|
|
|
Re: Tarball issues
By: mirek on Mon, 16 January 2017 11:20
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Mon, 16 January 2017 00:51
|
|
|
Re: Tarball issues
By: Klugier on Sat, 14 January 2017 22:40
|
|
|
Re: Tarball issues
By: amrein on Sat, 14 January 2017 22:50
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 17:47
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 17:50
|
|
|
Re: Tarball issues
By: Klugier on Sun, 15 January 2017 21:38
|
|
|
Re: Tarball issues
By: Klugier on Sun, 15 January 2017 22:13
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 23:37
|
|
|
Re: Tarball issues
By: amrein on Sun, 15 January 2017 21:37
|
|
|
Re: Tarball issues
By: amrein on Mon, 16 January 2017 19:21
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Tue, 17 January 2017 09:23
|
|
|
Re: Tarball issues
By: amrein on Tue, 17 January 2017 09:37
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Tue, 17 January 2017 19:01
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Wed, 18 January 2017 07:49
|
|
|
Re: Tarball issues
|
|
|
Re: Tarball issues
By: amrein on Wed, 18 January 2017 13:44
|
|
|
Re: Tarball issues
|
Goto Forum:
Current Time: Fri Mar 29 10:00:32 CET 2024
Total time taken to generate the page: 0.02038 seconds
|