mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] glib: version bump 2.52.1 -> 2.54.2
Date: Wed, 22 Nov 2017 10:20:49 +0000	[thread overview]
Message-ID: <216dd862-0581-b93a-abf4-fca88bbb7f39@mev.co.uk> (raw)
In-Reply-To: <20171122090532.kx5pbjbor75kx77n@pengutronix.de>

On 22/11/17 09:05, Michael Olbrich wrote:
> On Wed, Nov 22, 2017 at 12:18:07AM +0100, Ladislav Michl wrote:
>> Update to latest stable version.
>>
>> Also it turned out that package install stage is using GTKDOC tools
>> found on build host, so add empty ac_cv_path_* to avoid that.
>>
>> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
>> ---
>>   Note: See also previous mail. Perhaps it would be worth to create
>>   some global for disabling gtk-doc and ac_cv_path_* overriding...
>>   I'll leave this for later; consider this patch a bugfix ;)
> 
> Can you check if other packages are affected too? I think gnutls or
> gstreamer1 might be from what I can tell from reading the Makefiles.
> 
> If they are affected, then I'll work on a more general solution.
> 
> Michael

On my system, udev-legacy was one of the failing packages.  I got errors 
such as these:

Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
Traceback (most recent call last):
   File "/usr/bin/gtkdoc-rebase", line 56, in <module>
     sys.exit(rebase.run(options))
   File "/usr/share/gtk-doc/python/gtkdoc/rebase.py", line 66, in run
     dir = common.GetModuleDocDir('glib-2.0')
   File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 104, in 
GetModuleDocDir
     path = subprocess.check_output([config.pkg_config, 
'--variable=prefix', module_name], universal_newlines=True)
   File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
     raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', 
'--variable=prefix', 'glib-2.0']' returned non-zero exit status 1
make[4]: *** [install-data-local] Error 1
Makefile:772: recipe for target 'install-data-local' failed
make[3]: *** [install-am] Error 2
Makefile:500: recipe for target 'install-am' failed
make[2]: *** [install-recursive] Error 1
Makefile:3190: recipe for target 'install-recursive' failed
make[1]: *** [install] Error 2
Makefile:3668: recipe for target 'install' failed
make[1]: Leaving directory 
'/mnt/lindata/work/abbotti/ptxdist/projects/testproject/platform-EBV-Socrates/build-target/udev-182'


I worked around it by uninstalling the Debian host's gtk-doc-tools package.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2017-11-22 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 23:18 Ladislav Michl
2017-11-22  9:05 ` Michael Olbrich
2017-11-22 10:16   ` Ladislav Michl
2017-11-22 10:20   ` Ian Abbott [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=216dd862-0581-b93a-abf4-fca88bbb7f39@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox