[blfs-support] Poppler 0.65.0 using python3

[Christopher Gregory]

Sent: Thursday, June 07, 2018 at 1:39 AM
Subject: Re: [blfs-support] Poppler 0.65.0 using python3
...

[ 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
  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
  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
glib/Poppler-0.18.gir] Error 1
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.
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.

Is /usr/bin/cc a valid symlink? It's not a python problem, but
g-ir-scanner/g-ir-compiler one.
From memory, they hardcode /usr/bin/cc somewhere ... Try rebuilding
gobject-introspection with CC=gcc ./configure ... if /usr/bin/cc is
valid ...
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Hello Armin,

Thanks for that pointer.

I rebuilt gobject-introspection-1.56.1 with CC=gcc CXX=g++ \ ./configure ....

and tried again with poppler, and got the same error.

I then deleted the poppler directory re-extracted it and added CC=gcc CXX=g++ before the make command and poppler successfully compiled the shared library.

From what I can tell /usr/bin/cc is a valid symlink:

root [ /opt/sources ]# ls -al /usr/bin/cc
lrwxrwxrwx 1 root root 3 Jun 3 17:24 /usr/bin/cc -> gcc

The question now is, will this need to be added into the book when BLFS goes to gcc-8.1.0, or is it just an oddity with my installation?

I built LFS with jhalf and I never mess with the symlinks, from what is described in the book instructions, so I can not understand why this should happen.

Regards,

Christopher.

[Christopher Gregory]

[niuneilneo]

[William Harrington]

Harrington, go FUCK YOURSELF. This is blfs-SUPPORT mailing list you dumb
fucking piece of garbage.

Hello Christopher,

Your lack of life degrades your being. Go read up on the history of the word fuck and see what you come up with. May as well look up phuck, too.

Yes, it is BLFS support. Not giving your whole life about what you do support is suggestive. You are not the only misinformed being. If you get a new free e-mail account we don't care. Capisce? If you have a new baby or car or if you think a baby is a car, go to LFS-Chat.

Sincerely,

William Harrington

[Christopher Gregory]

Sent: Thursday, June 07, 2018 at 2:13 AM
Subject: Re: [blfs-support] Poppler 0.65.0 using python3

Harrington, go FUCK YOURSELF. This is blfs-SUPPORT mailing list you dumb
fucking piece of garbage.

Hello Christopher,
Your lack of life degrades your being. Go read up on the history of the word fuck and see what you come up with. May as well look up phuck, too.
Yes, it is BLFS support. Not giving your whole life about what you do support is suggestive. You are not the only misinformed being. If you get a new free e-mail account we don't care. Capisce? If you have a new baby or car or if you think a baby is a car, go to LFS-Chat.
Sincerely,
William Harrington
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Harrington,

I really do not care WHAT the hell you think of me. The planet would be a far better place without you in it. As you won't do the world a favor and leave it voluntarily, hopefully someone
will get sick enough of you to cut your worthless throat.

May that day be TODAY.

[Bruce Dubbs]

All who are relying to this thread: Drop the personal comments or I
will put you in moderated status.

-- Bruce

[Dr. - Ing. Edgar Alwers]

Is this the "academic" way nowadays to discuss cientific issues? Shame! Come down to civilisized manners or leave these forums!!

Von meinem Xperia™ Smartphone von Sony gesendet

---- William Harrington schrieb ----

Post by William Harrington

Harrington, go FUCK YOURSELF. This is blfs-SUPPORT mailing list you dumb
fucking piece of garbage.

Hello Christopher,
Your lack of life degrades your being. Go read up on the history of the word fuck and see what you come up with. May as well look up phuck, too.
Yes, it is BLFS support. Not giving your whole life about what you do support is suggestive. You are not the only misinformed being. If you get a new free e-mail account we don't care. Capisce? If you have a new baby or car or if you think a baby is a car, go to LFS-Chat.
Sincerely,
William Harrington
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[Bruce Dubbs]

Post by Christopher Gregory
root [ /opt/sources ]# ls -al /usr/bin/cc
lrwxrwxrwx 1 root root 3 Jun 3 17:24 /usr/bin/cc -> gcc
The question now is, will this need to be added into the book when BLFS goes to gcc-8.1.0, or is it just an oddity with my installation?
I built LFS with jhalf and I never mess with the symlinks, from what is described in the book instructions, so I can not understand why this should happen.

/usr/bin/cc is set in LFS. It does not need to be reset. You should
not need to specify CC=gcc CXX=g++ unless we say it's needed in the
book. The only places are llvm, cups, and optionally python3 in BLFS
(BUILDCC=gcc in vlc).

-- Bruce