Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Please help on emerging openssl
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
guoyingshou
n00b
n00b


Joined: 08 Jan 2014
Posts: 10

PostPosted: Wed Jan 02, 2019 7:04 am    Post subject: Please help on emerging openssl Reply with quote

It's been a while since I'm not able to emerge openssl. The build log is:

Code:
^[[32;01m * ^[[39;49;00mPackage:    dev-libs/openssl-1.1.0j
^[[32;01m * ^[[39;49;00mRepository: gentoo
^[[32;01m * ^[[39;49;00mMaintainer: base-system@gentoo.org
^[[32;01m * ^[[39;49;00mUSE:        abi_x86_32 abi_x86_64 amd64 asm cpu_flags_x86_sse2 elibc_glibc kernel_linux userland_GNU zlib
^[[32;01m * ^[[39;49;00mFEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking openssl-1.1.0j.tar.gz to /var/tmp/portage/dev-libs/openssl-1.1.0j/work
>>> Source unpacked in /var/tmp/portage/dev-libs/openssl-1.1.0j/work
>>> Preparing source in /var/tmp/portage/dev-libs/openssl-1.1.0j/work/openssl-1.1.0j ...
 ^[[32;01m*^[[0m Applying openssl-1.0.2a-x32-asm.patch ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m Applying openssl-1.1.0j-parallel_install_fix.patch ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
Operating system: x86_64-whatever-dbus gudev opengl threads acpi v41 v412 alsa
This system (dbus gudev opengl threads acpi v41 v412 alsa) is not supported. See file INSTALL for details.
 ^[[31;01m*^[[0m ERROR: dev-libs/openssl-1.1.0j::gentoo failed (prepare phase):
 ^[[31;01m*^[[0m   I AM NOT SANE
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m     ebuild.sh, line 124:  Called src_prepare
 ^[[31;01m*^[[0m   environment, line 2834:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m       ./config --test-sanity || die "I AM NOT SANE";
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=dev-libs/openssl-1.1.0j::gentoo'`,
 ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.1.0j::gentoo'`.
 ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.1.0j/temp/build.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.1.0j/temp/environment'.
 ^[[31;01m*^[[0m Working directory: '/var/tmp/portage/dev-libs/openssl-1.1.0j/work/openssl-1.1.0j'
 ^[[31;01m*^[[0m S: '/var/tmp/portage/dev-libs/openssl-1.1.0j/work/openssl-1.1.0j'


I wonder what is the meaning of the message "This system (dbus gudev opengl threads acpi v41 v412 alsa) is not supported."

My emerege --info results are:


Code:
Portage 2.3.53 (python 3.6.6-final-0, default/linux/amd64/17.0/systemd, gcc-8.2.0, glibc-2.28-r4, 4.20.0-gentoo x86_64)
=================================================================
System uname: Linux-4.20.0-gentoo-x86_64-Intel-R-_Core-TM-_i7-4712HQ_CPU_@_2.30GHz-with-gentoo-2.6
KiB Mem:    16316708 total,  11015968 free
KiB Swap:    2097148 total,   2097148 free
Timestamp of repository gentoo: Wed, 02 Jan 2019 02:45:01 +0000
Head commit of repository gentoo: 9f8a859969a42c4a13b8c9bd04409b84197befd6
sh bash 4.4_p23
ld GNU ld (Gentoo 2.31.1 p5) 2.31.1
app-shells/bash:          4.4_p23::gentoo
dev-lang/perl:            5.26.2::gentoo
dev-lang/python:          2.7.15::gentoo, 3.5.5-r1::gentoo, 3.6.6::gentoo
dev-util/cmake:           3.13.2::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.6-r1::gentoo
sys-apps/sandbox:         2.14::gentoo
sys-devel/autoconf:       2.13-r1::gentoo, 2.69-r4::gentoo
sys-devel/automake:       1.16.1-r1::gentoo
sys-devel/binutils:       2.31.1-r3::gentoo
sys-devel/gcc:            8.2.0-r6::gentoo
sys-devel/gcc-config:     2.0::gentoo
sys-devel/libtool:        2.4.6-r5::gentoo
sys-devel/make:           4.2.1-r4::gentoo
sys-kernel/linux-headers: 4.20::gentoo (virtual/os-headers)
sys-libs/glibc:           2.28-r4::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://rsync.au.gentoo.org/gentoo-portage
    priority: -1000
    sync-rsync-extra-opts:
    sync-rsync-verify-max-age: 24
    sync-rsync-vcs-ignore: true
    sync-rsync-verify-metamanifest: no
    sync-rsync-verify-jobs: 1

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=haswell -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt /var/bind"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=haswell -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirrors.163.com/gentoo/"
LANG="zh_CN.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en_US en zh_CN"
MAKEOPTS="-j9"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X acl acpi aes alsa amd64 avx avx2 berkdb build bzip2 cairo caps cjk cli crypt cxx dbus dell dhclient dlz dmx dri expat f16c ffmpeg fma3 fortran gdbm gentoo-vm glib gtk3 gudev iconv icu ieee1394 ipv6 jpeg laptop lcdfilter libtirpc lm_sensors lua mmx mmxext multilib ncurses nls nptl ogg openal opengl openmp orc pam pclmul pcre png policykit popcnt pulseaudio qt3support readline sdl seccomp sqlite sse sse2 sse3 sse4_1 sse4_2 ssl ssse3 symlink systemd tcpd threads tiff touchscreen truetype tslib udev udisks unicode v41 v412 vorbis wext xattr xinerama xorg zlib" ABI_X86="64 32" ALSA_CARDS="hda_intel usb_audio" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon plan sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="efi-6" INPUT_DEVICES="libinput synaptics" KERNEL="linux" L10N="en-US en zh-CN" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6 php7-1" POSTGRES_TARGETS="postgres9_5 postgres10" PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" RUBY_TARGETS="ruby23 ruby25" USERLAND="GNU" VIDEO_CARDS="intel i965" XFCE_PLUGINS="brightness clock trash" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

Any helps/hints are really appreciated!

[Moderator edit: added [code] tags to preserve output layout. -Hu]
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21754
Location: here

PostPosted: Wed Jan 02, 2019 7:05 am    Post subject: Reply with quote

You can post your make.conf?
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
guoyingshou
n00b
n00b


Joined: 08 Jan 2014
Posts: 10

PostPosted: Wed Jan 02, 2019 7:09 am    Post subject: Reply with quote

Code:
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-march=haswell -O2 -pipe"
#CFLAGS="-O2 -pipe"
CXXFLAGS="${CFLAGS}"
#LDFLAGS="$LDFLAGS -ldl"
LDFLAGS="$LDFLAGS"
CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
NOTUSE="-hal -bindist -dhcpcd -ppp -modemmanager -qt4 -gnome -kde -consolekit"
#RUBYUSE="ruby_targets_ruby23 ruby_targets_ruby25"
RUBY_TARGETS="ruby23 ruby25"
#SYSTEM="dbus gudev nvidia xvmc tools opengl threads acpi ssse3 sse4_1 sse4_2 v41 v412 alsa"
SYSTEM="dbus gudev opengl threads acpi  v41 v412 alsa"
NOTEBOOK="laptop dell ieee1394 lcdfilter lm_sensors"
USE="${CPU_FLAGS_X86} ${SYSTEM} ${NOTEBOOK} ${NOTUSE} ${RUBYUSE} \
     openmp ogg vorbis qt3support symlink pulseaudio caps glib orc gtk3 \
     policykit X udisks icu \
     -qt5 \
     sqlite \
     ffmpeg tiff openal sdl expat \
     cjk nls unicode dhclient \
     jpeg png touchscreen xorg tslib nptl dmx udev dlz cairo \
     lua wext \
     build \
     gentoo-vm \
     truetype xinerama"
PORTDIR="/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"

GRUB_PLATFORMS="efi-6"
ACCEPT_KEYWORDS="~amd64"
#ACCEPT_KEYWORDS="amd64"
MAKEOPTS="-j9"
VIDEO_CARDS="intel i965"
#VIDEO_CARDS="i965 nvidia"
#INPUT_DEVICES="evdev synaptics"
INPUT_DEVICES="libinput synaptics"
XFCE_PLUGINS="brightness clock trash"
ALSA_CARDS="hda_intel usb_audio"
LINGUAS="en_US en zh_CN"
L10N="en-US en zh-CN"
ACCEPT_LICENSE="*"
ABI_X86="64 32"

# added when emerge blender
#PYTHON_TARGETS="python2_7 python3_6 pypy"
#PYTHON_SINGLE_TARGET="python2_7"
#USE_PYTHON='2.7 3.5'

GENTOO_MIRRORS="http://mirrors.163.com/gentoo/"


[Moderator edit: added [code] tags to preserve output layout. -Hu]
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21754
Location: here

PostPosted: Wed Jan 02, 2019 7:11 am    Post subject: Reply with quote

Change SYSTEM variable on make.conf, for example with _SYSTEM, because it is used by openssl and then cause error
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
guoyingshou
n00b
n00b


Joined: 08 Jan 2014
Posts: 10

PostPosted: Wed Jan 02, 2019 7:17 am    Post subject: Reply with quote

@fedeliallalinea

It works!

Lots of thanks!!!
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13830

PostPosted: Thu Jan 03, 2019 2:39 am    Post subject: Reply with quote

guoyingshou wrote:
Code:
LDFLAGS="$LDFLAGS"
This line is useless and can be removed.
guoyingshou wrote:
Code:
NOTUSE="-hal -bindist -dhcpcd -ppp -modemmanager -qt4 -gnome -kde -consolekit"
SYSTEM="dbus gudev opengl threads acpi  v41 v412 alsa"
NOTEBOOK="laptop dell ieee1394 lcdfilter lm_sensors"
These lines are wrong and should be removed. You should not invent your own names in make.conf. Use only well-defined variable names. Otherwise, as here, you pollute the build environment and get strange failures.
Back to top
View user's profile Send private message
KatsuoRyuu
n00b
n00b


Joined: 08 Nov 2016
Posts: 43

PostPosted: Mon Jan 07, 2019 4:06 am    Post subject: Reply with quote

Hu wrote:
guoyingshou wrote:
Code:
LDFLAGS="$LDFLAGS"
This line is useless and can be removed.
guoyingshou wrote:
Code:
NOTUSE="-hal -bindist -dhcpcd -ppp -modemmanager -qt4 -gnome -kde -consolekit"
SYSTEM="dbus gudev opengl threads acpi  v41 v412 alsa"
NOTEBOOK="laptop dell ieee1394 lcdfilter lm_sensors"
These lines are wrong and should be removed. You should not invent your own names in make.conf. Use only well-defined variable names. Otherwise, as here, you pollute the build environment and get strange failures.


On the other hand the fact that a "soft" defined variable like SYSTEM is being used in OpenSSL is really bad, and/or the variables from make.conf is not actually encapsulated in a way that's not going to screw with other stuff in this manner.


- To be honest I think the portage system really need to be improved, which is the reason I'm playing around with rebuilding it in Rust. But that for another thread.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13830

PostPosted: Mon Jan 07, 2019 4:38 am    Post subject: Reply with quote

If you want to rewrite Portage, please rewrite it in a language that has a sane base.
Back to top
View user's profile Send private message
toralf
Developer
Developer


Joined: 01 Feb 2004
Posts: 3684
Location: Hamburg

PostPosted: Mon Jan 07, 2019 7:49 am    Post subject: Reply with quote

fedeliallalinea wrote:
YSTEM variable ...is used by openssl
Interesting, may I asked where, in their configure step?
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21754
Location: here

PostPosted: Mon Jan 07, 2019 7:54 am    Post subject: Reply with quote

toralf wrote:
fedeliallalinea wrote:
YSTEM variable ...is used by openssl
Interesting, may I asked where, in their configure step?

Yes in config script
Code:
...
[ "$SYSTEM" ] || SYSTEM=`(uname -s) 2>/dev/null`  || SYSTEM="unknown"
...

_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
KatsuoRyuu
n00b
n00b


Joined: 08 Nov 2016
Posts: 43

PostPosted: Mon Jan 07, 2019 11:35 am    Post subject: Reply with quote

Hu wrote:
If you want to rewrite Portage, please rewrite it in a language that has a sane base.


Rust does have has a sane base. but will agree that (okay now i end up sounding rude again, sorry in advance), it does require you to actually know what you are doing and have a proper skill set. Most in my current company is what i would call Script Kitties, so they wouldn't be able to program in Rust without mashing everything up.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13830

PostPosted: Tue Jan 08, 2019 2:49 am    Post subject: Reply with quote

KatsuoRyuu wrote:
Hu wrote:
If you want to rewrite Portage, please rewrite it in a language that has a sane base.
Rust does have has a sane base. but will agree that (okay now i end up sounding rude again, sorry in advance), it does require you to actually know what you are doing and have a proper skill set. Most in my current company is what i would call Script Kitties, so they wouldn't be able to program in Rust without mashing everything up.
As I interpret the comments in Debian, Rust, and librsvg, no, Rust does not have a sane base. Their install instructions earn them a spot on the curlpipesh blog. They actually suggest this as the installation method:
https://www.rust-lang.org/tools/install:
curl https://sh.rustup.rs -sSf | sh
Their second choice for installation is "Download this prebuilt binary for your architecture, and just trust that we didn't screw it up."

I'm not even looking at how easy or hard it is to use the language. I glanced at some examples of Rust, but I've never tried to use it because I looked at the install instructions and decided they couldn't be serious. Look at how absurdly painful it is to package. As I understand that LWN thread, to install a rust compiler, you need a working Rust compiler from the immediately preceding release (and sometimes you can get away with jumping more than one version at once, but it's not guaranteed to work). If you don't have a working Rust compiler, you can either download one from the Rust authors or you can go back to the very very early rust sources, build one of those with OCaml, then build your way forward. No one has admitted to having documentation or scripts to do this. Further, Rust bundles LLVM and only works on targets where LLVM support is good. If you want Rust on a target that doesn't have LLVM, you get to patch LLVM too.

The six week release cycle is a nasty choice with such minimal backward compatibility guarantees. Short release cycles can be good, if you don't force everyone to chase along behind you. (In this case, that would mean that they guarantee you can bootstrap using a Rust that is, say - 6-9 months old.) Some distributions might otherwise skip several releases if they wanted to ship only the Rust that was stable at freeze time, but with the minimal backward compatibility guarantees, that will inevitably lead to trouble.

To me, a sane base requires that it can be bootstrapped from source using commonly available tools: bash, Python, Perl, gcc, etc. Preferably, it should work with the versions of those tools that are standard on the latest release of the major distributions.

I'm also strongly biased against anyone whose preferred install instructions start with a curl|sh construct. That practically screams "You cannot trust us to make good decisions."
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5760

PostPosted: Tue Jan 08, 2019 8:25 am    Post subject: Reply with quote

Hu wrote:
To me, a sane base requires that it can be bootstrapped from source using commonly available tools: bash, Python, Perl, gcc, etc. Preferably, it should work with the versions of those tools that are standard on the latest release of the major distributions.

Might I suggest Perl 6? They're making an effort to pass Debian Sta(b)le QA right now, which requires it works on *all* of their supported platforms including weird ones; it's a superset of what Gentoo officially supports. That suggests they actually care about being installable everywhere. Also the code's a bit easier for human beings to read ;)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum