a doc which describes what they are & what they do ?
$ qfile `man -w mozcoreconf-v6.eclass`
app-doc/eclass-manpages (/usr/share/man/man5/mozcoreconf-v6.eclass.5.gz)
HTH,
-dnh
--
Less is more or less more
e will have more experience and practical advice
regarding this, but one thing I noticed in the ebuild code above:
have you tried using the meson eclass?
(man meson.eclass, if you have app-doc/eclass-manpages)
--
Nuno Silva
On Tue, Jan 13, 2015 at 7:10 PM, walt w41...@gmail.com wrote:
After searching various portage manpages and grepping through the eclass
directory I can find only one pathetic reference to ABI_X86 in a Changelog,
which doesn't give me clue where the variable is defined.
It's a typical use
.
I can tell from the info you provided that you already know more about
the subject than I do.
So I'll supply questions instead of answers :)
After searching various portage manpages and grepping through the eclass
directory I can find only one pathetic reference to ABI_X86 in a Changelog,
which
/eclass-manpages
app-portage/porthole
app-shells/zsh
app-text/enscript
app-text/hunspell
app-text/libwpd
app-text/linuxdoc-tools
app-text/psutils
app-text/rcs
app-text/recode
app-text/wv2
dev-cpp/commoncpp2
dev-cpp/libebt
dev-cpp/libsexymm
dev-cpp/libwrapiter
dev-cpp/libxmlpp
dev-db/qdbm
ffloading
(accel) compiler as follows:
1. Use crossdev like when building a regular cross-compiler:
# crossdev -v -t x86_64-intelmicemul-linux-gnu #for intel MIC
or
# crossdev -v -t nvptx-none # for nvidia ptx
2. As soon as it start building the 1st stage, hit CTRL-C
3. cd to your crossd
ts/tests@@@as-test_yaml@exe/as-test-utils.c.o' -c ../appstream-APPSTREAM_0_11_5/tests/as-test-utils.c
[44/106] /usr/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 -o docs/appstreamcli.1 http://docbook.sourceforge.ne
7 matches
Mail list logo
