Failed to import the site module
Traceback (most recent call last):
  File "/usr/lib/python3.4/site.py", line 74, in <module>
    import _sitebuiltins
SystemError: Negative size passed to PyUnicode_New
 * ERROR: sys-libs/glibc-2.24-r3::gentoo failed (prerm phase):
 *   filter-bash-environment.py failed
 * 
 * Call stack:
 *            ebuild.sh, line 538:  Called __preprocess_ebuild_env
 *   phase-functions.sh, line 156:  Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   phase-functions.sh, line 137:  Called die
 * The specific snippet of code:
 *   	"${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
Traceback (most recent call last):
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 9, in <module>
    import logging
  File "/usr/lib/python3.4/logging/__init__.py", line 26, in <module>
    import sys, os, time, io, traceback, warnings, weakref, collections
  File "/usr/lib/python3.4/traceback.py", line 3, in <module>
    import linecache
  File "/usr/lib/python3.4/linecache.py", line 10, in <module>
    import tokenize
  File "/usr/lib/python3.4/tokenize.py", line 32, in <module>
    import re
  File "/usr/lib/python3.4/re.py", line 123, in <module>
    import sre_compile
SystemError: Negative size passed to PyUnicode_New
 * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
Failed to import the site module
Traceback (most recent call last):
  File "/usr/lib/python3.4/site.py", line 72, in <module>
    import os
  File "/usr/lib/python3.4/os.py", line 57, in <module>
    import posixpath as path
  File "/usr/lib/python3.4/posixpath.py", line 16, in <module>
    import genericpath
SystemError: Negative size passed to PyUnicode_New
 * ERROR: sys-libs/glibc-2.24-r3::gentoo failed:
 *   filter-bash-environment.py failed
 * 
 * Call stack:
 *    misc-functions.sh, line  17:  Called source '/usr/lib/portage/python3.4/ebuild.sh'
 *            ebuild.sh, line 538:  Called __preprocess_ebuild_env
 *   phase-functions.sh, line 156:  Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   phase-functions.sh, line 137:  Called die
 * The specific snippet of code:
 *   	"${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
Traceback (most recent call last):
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 11, in <module>
    import pickle
  File "/usr/lib/python3.4/pickle.py", line 1560, in <module>
    from _pickle import (
SystemError: Negative size passed to PyUnicode_New
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED prerm: 1
Failed to import the site module
Traceback (most recent call last):
  File "/usr/lib/python3.4/site.py", line 74, in <module>
    import _sitebuiltins
SystemError: Negative size passed to PyUnicode_New
 * ERROR: sys-libs/glibc-2.24-r3::gentoo failed (postrm phase):
 *   filter-bash-environment.py failed
 * 
 * Call stack:
 *            ebuild.sh, line 538:  Called __preprocess_ebuild_env
 *   phase-functions.sh, line 156:  Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   phase-functions.sh, line 137:  Called die
 * The specific snippet of code:
 *   	"${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
Traceback (most recent call last):
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 9, in <module>
    import logging
  File "/usr/lib/python3.4/logging/__init__.py", line 26, in <module>
    import sys, os, time, io, traceback, warnings, weakref, collections
  File "/usr/lib/python3.4/traceback.py", line 3, in <module>
    import linecache
  File "/usr/lib/python3.4/linecache.py", line 10, in <module>
    import tokenize
  File "/usr/lib/python3.4/tokenize.py", line 32, in <module>
    import re
  File "/usr/lib/python3.4/re.py", line 123, in <module>
    import sre_compile
SystemError: Negative size passed to PyUnicode_New
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
Failed to import the site module
Traceback (most recent call last):
  File "/usr/lib/python3.4/site.py", line 72, in <module>
    import os
  File "/usr/lib/python3.4/os.py", line 57, in <module>
    import posixpath as path
  File "/usr/lib/python3.4/posixpath.py", line 16, in <module>
    import genericpath
SystemError: Negative size passed to PyUnicode_New
 * ERROR: sys-libs/glibc-2.24-r3::gentoo failed:
 *   filter-bash-environment.py failed
 * 
 * Call stack:
 *    misc-functions.sh, line  17:  Called source '/usr/lib/portage/python3.4/ebuild.sh'
 *            ebuild.sh, line 538:  Called __preprocess_ebuild_env
 *   phase-functions.sh, line 156:  Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   phase-functions.sh, line 137:  Called die
 * The specific snippet of code:
 *   	"${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
Traceback (most recent call last):
  File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 11, in <module>
    import pickle
  File "/usr/lib/python3.4/pickle.py", line 1560, in <module>
    from _pickle import (
SystemError: Negative size passed to PyUnicode_New
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED postrm: 1
 * The 'postrm' phase of the 'sys-libs/glibc-2.24-r3' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'glibc-2.24-r3.ebuild' located in the '/var/db/pkg/sys-
 * libs/glibc-2.24-r3' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.