On Sat, 2 Sep 2017 12:53:05 +0930 Simon Lees <sfl...@suse.de> said:
>
>
> On 02/09/17 10:51, Carsten Haitzler (The Rasterman) wrote:
> > On Fri, 1 Sep 2017 20:38:59 +0200 marcel-hollerb...@t-online.de said:
> >
> >> On Fri, Sep 01, 2017 at 08:07:18PM +0200, Davide Andreoli wrote:
> >>> 2017-09-01 19:50 GMT+02:00 Mike Blumenkrantz
> >>> <michael.blumenkra...@gmail.com
> >>>> :
> >>>
> >>>> It seems that the two build systems have fallen out of sync far faster
> >>>> than I expected, and the autotools build is both no longer functional and
> >>>> cannot provide a dist which is able to build using meson.
> >>>>
> >>>> I'm not particularly interested in putting in even more work to try and
> >>>> maintain something which is pending removal, so if anyone is super
> >>>> interested in keeping it for the E22 release then patches are welcome,
> >>>> otherwise I'll plan to remove autotools entirely next week before
> >>>> starting the official release cycle.
> >>>>
> >>>
> >>> +1
> >>>
> >>
> >> +1
> >>
> >> Just probebly checking if meson versions etc. fit the most distros, so
> >> we dont leave users behind.
> >
> > i think then autogen.sh should do what rage does and do a meson build setup
> > and fix appropriate INSTALL files etc. for how to build...
> >
> > but we also should get some decent testing across multiple OS's like
> > freebsd, openbsd (i know netstar maintains these as running systems ! :)).
> > to ensure at least on a lot of targets it builds right. package maintainers
> > too would be really fantastic if they could switch and test there too in
> > package build env's
> >
>
> Speaking with a distro maintainers hat on, for this to be usable there
> needs to be considerably more documentation, neither meson --help,
> README or README.wayland tell me how to enable or disable building with
> git. All that stuff simply should be there before you get distro's to
> try it (or intend to remove autotools) otherwise your just wasting our
> time. Equally the html documentation is not built automatically and
> there is no indication of how one might build it.
copying the above docs over and autogen.sh over would solve that. i can do it
now if you want... but it's mean autogen is now meson not autofoo so autofoo
build will effectively be disabled for most people.
> As a side note, git is also required for building (which wasn't the case
> before).
that is actually incorrect. git is required to create the dist tarball only.
the dist tarball can be built with no problems from there - no git needed. at
least in the general sense -- try rage (far smaller so faster/simpler to test).
do a dist. the INSTALL documents how to do it:
ninja -C build dist
after you configured for meson:
meson . build
in build/meson-dist you'll find the dist tarball (and checksum file) take THAT
tarball and build it exactly as instructions for normal building and
configuring. no problems. no git needed.
> In terms of distro support and success covering our currently supported
> distro's:
>
> openSUSE Tumbleweed: Works fine
> openSUSE Leap 42.3: Meson Crashes [1]
> openSUSE Leap 42.2: Meson version is too old or not available.
>
> So from a distro perspective there is still some work to be done here
> before we can consider dropping autotools.
docs are basically done. just copy them over from rage. i did the work on a
smaller project. dist stuff is done. it's really testing to be done.
> 1.
> https://build.opensuse.org/package/live_build_log/X11:Enlightenment:Nightly/enlightenment/openSUSE_Leap_42.3/x86_64
>
>
>
> [ 70s] + /usr/bin/meson --buildtype=plain --prefix=/usr
> --libdir=/usr/lib64 --libexecdir=/usr/lib --bindir=/usr/bin
> --sbindir=/usr/sbin --includedir=/usr/include --datadir=/usr/share
> --mandir=/usr/share/man --infodir=/usr/share/info
> --localedir=/usr/share/locale --sysconfdir=/etc --localstatedir=/var
> --sharedstatedir=/usr/com . build
> [ 71s] Traceback (most recent call last):
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/mesonmain.py", line 298, in run
> [ 71s] app.generate()
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/mesonmain.py", line 180, in
> generate
> [ 71s] intr.run()
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreter.py", line 2504,
> in run
> [ 71s] super().run()
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 125, in run
> [ 71s] self.evaluate_codeblock(self.ast, start=1)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 146, in evaluate_codeblock
> [ 71s] raise e
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 140, in evaluate_codeblock
> [ 71s] self.evaluate_statement(cur)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 153, in evaluate_statement
> [ 71s] return self.assignment(cur)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 566, in assignment
> [ 71s] value = self.evaluate_statement(node.value)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 151, in evaluate_statement
> [ 71s] return self.function_call(cur)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreterbase.py", line
> 372, in function_call
> [ 71s] return self.funcs[func_name](node, self.flatten(posargs),
> kwargs)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreter.py", line 1494,
> in func_run_command
> [ 71s] get_meson_script(self.environment, 'mesonintrospect'),
> in_builddir)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreter.py", line 77,
> in __init__
> [ 71s] pc, self.stdout, self.stderr =
> self.run_command(command_array, source_dir, build_dir, subdir,
> mesonintrospect, in_builddir)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/interpreter.py", line 98,
> in run_command
> [ 71s] return Popen_safe(command_array, env=child_env, cwd=cwd)
> [ 71s] File
> "/usr/lib/python3.4/site-packages/mesonbuild/mesonlib.py", line 510, in
> Popen_safe
> [ 71s] stderr=stderr, **kwargs)
> [ 71s] File "/usr/lib64/python3.4/subprocess.py", line 856, in __init__
> [ 71s] restore_signals, start_new_session)
> [ 71s] File "/usr/lib64/python3.4/subprocess.py", line 1460, in
> _execute_child
> [ 71s] raise child_exception_type(errno_num, err_msg)
> [ 71s] PermissionError: [Errno 13] Permission denied
> [ 71s] The Meson build system
> [ 71s] Version: 0.40.1
> [ 71s] Source dir:
> /home/abuild/rpmbuild/BUILD/enlightenment-0.21.99.20170901.cc5eec5cc
> [ 71s] Build dir:
> /home/abuild/rpmbuild/BUILD/enlightenment-0.21.99.20170901.cc5eec5cc/build
> [ 71s] Build type: native build
> [ 71s] Project name: enlightenment
> [ 71s] Native c compiler: cc (gcc 4.8.5)
> [ 71s] Appending CFLAGS from environment: '-fmessage-length=0
> -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
> -funwind-tables -fasynchronous-unwind-tables -g'
> [ 71s] Build machine cpu family: x86_64
> [ 71s] Build machine cpu: x86_64
> [ 71s] error: Bad exit status from /var/tmp/rpm-tmp.c16M02 (%build)
>
> --
>
> Simon Lees (Simotek) http://simotek.net
>
> Emergency Update Team keybase.io/simotek
> SUSE Linux Adelaide Australia, UTC+10:30
> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
>
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) ras...@rasterman.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
