Hi,

I have just compiled and installed poppler 0.62 successfully. So is there any necessity for you to use newer poppler instead of 0.62 version?

Yours,
Lei


发自网易邮箱大师
On 6/6/2018 17:37Christopher Gregory<[email protected]> wrote:
 
 
Sent: Wednesday, June 06, 2018 at 3:25 PM
From: "Christopher Gregory" <[email protected]>
To: [email protected]
Subject: [blfs-support] Poppler 0.65.0 using python3
Hello,
 
I have signed up for a free email account and registered this email address on blfs-support, in the hope that Ken etc will actually be able to get the emails I send.
 
I am unable to install poppler 0.65.0 OR poppler 0.64.0
This is a new install:
I took a snapshot of the blfs svn repository on the 2nd June after I had used jhalfs to build the then current version of systemd.
I have updated all of the gnome packages and other packages on my local repository to the latest versions, due to the fact that the online version of systemd is so far outdated that it is a joke.
Differences are:
gcc version is: 8.1.0
I made NO changes to the instructions in the book for jhalfs to compile LFS other than to blacklist openssl from optimization.
After lfs was completed, I logged into chroot and:
1) installed gpm, wget, changed root password and added a normal user. At that stage I copied the locally renderd blfs systemd book to the new build and rebooted.
2) From the console I then re-compiled gcc before I installed anything else.
The error I am getting is:

[ 79%] Built target poppler-glib
Scanning dependencies of target gir-typelibs
[ 79%] Generating Poppler-0.18.gir
unable to execute '-E': No such file or directory
Traceback (most recent call last):
  File "/usr/lib/python3.6/distutils/unixccompiler.py", line 107, in preprocess
    self.spawn(pp_args)
  File "/usr/lib/python3.6/distutils/ccompiler.py", line 909, in spawn
    spawn(cmd, dry_run=self.dry_run)
  File "/usr/lib/python3.6/distutils/spawn.py", line 36, in spawn
    _spawn_posix(cmd, search_path, dry_run=dry_run)
  File "/usr/lib/python3.6/distutils/spawn.py", line 159, in _spawn_posix
    % (cmd, exit_status))
distutils.errors.DistutilsExecError: command '-E' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/bin/g-ir-scanner", line 66, in <module>
    sys.exit(scanner_main(sys.argv))
  File "/usr/lib/gobject-introspection/giscanner/scannermain.py", line 538, in scanner_main
    ss = create_source_scanner(options, args)
  File "/usr/lib/gobject-introspection/giscanner/scannermain.py", line 446, in create_source_scanner
    ss.parse_files(filenames)
  File "/usr/lib/gobject-introspection/giscanner/sourcescanner.py", line 263, in parse_files
    self._parse(headers)
  File "/usr/lib/gobject-introspection/giscanner/sourcescanner.py", line 308, in _parse
    self._cpp_options)
  File "/usr/lib/gobject-introspection/giscanner/ccompiler.py", line 210, in preprocess
    extra_postargs=extra_postargs)
  File "/usr/lib/python3.6/distutils/unixccompiler.py", line 109, in preprocess
    raise CompileError(msg)
distutils.errors.CompileError: command '-E' failed with exit status 1
make[2]: *** [glib/CMakeFiles/gir-typelibs.dir/build.make:94: glib/Poppler-0.18.gir] Error 1
make[1]: *** [CMakeFiles/Makefile2:643: glib/CMakeFiles/gir-typelibs.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
I then re-installed glib omitting the use python3 switch and the building of poppler still failed.
Next I tried:
 
The previous version of poppler and the exact same results.
I then even tried downgrading cmake to the .2 release instead of the latest, again with the exact same failure.
 
I have also re-installed Python-3.6.5 and get the same failure.
 
Regards,
 
Christopher.
 
Well I seem to have made progress of sorts.  I disabled building the shared libraries and the build was successfull.   Does anyone have any ideas as to why building the shared libraries would fail?
 
Regards,
 
Christopher.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to