Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
building from scratch rootfs for armv7a-hardfloat
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Sun Oct 09, 2016 9:26 pm    Post subject: building from scratch rootfs for armv7a-hardfloat Reply with quote

Hi all.
Got emerge error after chroot - emerge says there is no such module (emerge) for python.
Trying building rootfs from scratch for armv7a-hardfloat-linux-gnueabi this way:

emerge crossdev
#emerge --ask crossdev

create armv7a-hf toolchain
#crossdev --stable --target armv7a-hardfloat-linux-gnueabi

adjust profile
#cd /usr/armv7a-hardfloat-linux-gnueabi/etc/portage && rm make.profile && ln -s /usr/portage/profiles/default/linux/arm/13.0/armv7a make.profile

adjust make.conf
#nano /usr/armv7a-hardfloat-linux-gnueabi/etc/portage/make.conf
put this to make conf:
Code:

########## BEGIN OF MAKE.CONF ##########
#THIS IS CROSSDEV armv7a-hardfloat-linux-gnueabi make.conf
CHOST="armv7a-hardfloat-linux-gnueabi"
CBUILD="x86_64-pc-linux-gnu"
ARCH="arm"
HOSTCC="x86_64-pc-linux-gnu-gcc"
CFLAGS="-O2 -pipe -fomit-frame-pointer -ftree-vectorize -fno-stack-protector -U_FORTIFY_SOURCE -march=armv7-a -mtune=cortex-a9 -mfpu=vfpv3-d16 -mfloat-abi=hard"
CXXFLAGS="${CFLAGS}"

MAKEOPTS="-j5"

ACCEPT_KEYWORDS="arm"
# at this time, dev-python/xattr-0.5.5 is not respect relative paths while emergin, disable it
# until it will, or emerge it in native env after chrooting; so we set now "-xattr"
USE="${ARCH} -acl fbdev -pam minimal threads -xattr"
FEATURES="collision-protect buildpkg noman noinfo nodoc parallel-fetch\
 parallel-install sandbox sfperms strict unknown-features-warn unmerge-logs\
 unmerge-orphans userfetch"

# ENV 4 CHOST SECTION
ELIBC="glibc"
ROOT="/usr/${CHOST}/"
PKGDIR="${ROOT}packages/"
PORTAGE_TMPDIR="${ROOT}tmp/"
PKG_CONFIG_PATH="${ROOT}usr/lib/pkgconfig/"
##PORTDIR_OVERLAY="/usr/portage/local/"
# !ENV 4 CHOST

## ENV 4 PAZ00 ROOTFS SECTION
## WITH THIS YOU SHOULD ALWAYS SPECIFY ROOT VAR before callin' emerge, if not chrooted
#ROOT=""
#PORTDIR="${ROOT}/usr/portage"
#DISTDIR="${PORTDIR}/distfiles"
#PKGDIR="${PORTDIR}/packages"
#PKG_CONFIG_PATH="${ROOT}/usr/lib/pkgconfig"
#PORTAGE_TMPDIR="${ROOT}/tmp"
# !ENV 4 PAZ

VIDEO_CARDS="fbdev tegra"

GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles/"
LINGUAS="en ru"
L10N="en ru"
########## END OF MAKE.CONF ##########


Building
First, i emerge latest gentoo-souces,
for this, allow ~arm in package.accept_keywords
#echo "sys-kernel/gentoo-sources ~arm" >> /usr/armv7a-hardfloat-linux-gnueabi/etc/portage/package.accept_keywords && echo "sys-kernel/linux-headers ~arm" >> /usr/armv7a-hardfloat-linux-gnueabi/etc/portage/package.accept_keywords

emerge kernel:
#armv7a-hardfloat-linux-gnueabi-emerge --nodeps gentoo-sources
#cd /usr/armv7a-hardfloat-linux-gnueabi/usr/src/linux-4.8.1 && make tegra_defconfig ARCH=arm && make menuconfig ARCH=arm

Well, now i have .config in CHOST rootfs.
now emerge @system,it will produce some errors, but we will fix them later
#armv7a-hardfloat-linux-gnueabi-emerge @system --keep-going -avt
emerge some other important packages:
#armv7a-hardfloat-linux-gnueabi-emerge --keep-going $(egrep '^[a-z]+' /usr/portage/profiles/default/linux/packages.build) -avt

Emerge <glib-2.48.2 fails on running macros m4 or something like that, so emerge ~arm version
#echo "dev-libs/glib ~arm" >> /usr/armv7a-hardfloat-linux-gnueabi/etc/portage/package.accept_keywords
emerge glib, glib-2.48.2 is generating another postinst error: "Failed to execute postinst for dev-libs/glib-2.48.2 for /usr/armv7a-hardfloat-linux-gnueabi/"
but glib installed, its cache update error, so we can ignore it?
#armv7a-hardfloat-linux-gnueabi-emerge -avt sys-devel/glib

now i got minimal rootfs with system. portage & other important things (python 2, 3, etc) ; dev & other system folders are created too.

Emerge qemu to host with "arm" targets and static useflags.
add qemu arm targets to host make.conf :
#echo "QEMU_SOFTMMU_TARGETS=arm" >> /etc/portage/make.conf && echo QEMU_USER_TARGETS="arm" >> /etc/portage/make.conf
add static useflags for qemu
#echo "app-emulation/qemu static-user" >> /etc/portage/package.use/gentoo_package.use
#emerge --buildpkg --oneshot qemu
install qemu into chrootfs
#cd /usr/armv7a-hardfloat-linux-gnueabi/
#ROOT=$PWD emerge qemu --oneshot --usepkgonly --nodeps

after this chroot to chost rootfs (using next script):
Code:

cd /usr/armv7a-hardfloat-linux-gnueabi/
mount --bind /proc proc
mount --bind /dev dev
mount --bind /sys sys
mount --bind /dev/pts dev/pts
mount --bind /usr/portage usr/portage
cp /etc/resolv.conf etc/resolv.conf
chroot . /bin/bash --login
umount usr/portage sys proc dev/pts dev


login ok, i got bash running and logged in
Then, calling emerge gives message that module emerge is not found.

Or, even if i chrooting to rootfs that was extracted from arm hf stage tarball, and after updating it with my toolchain (descrbed earlier) i got python error
ImportError: No module named 'portage'.
Before updating, emerge in chroot is working fine.
For update with my toolchain (without chroot and qemu) i use:
root/paz00_roorfs#ROOT=$PWD armv7a-hardfloat-linux-gnueabi-emerge @system --keep-going --update --deep --with-bdeps=y --newuse
where current directory (root/paz00_roorfs) is directory where stage tarball extracted; and make.conf portage varibles is set for PAZ00 section (see make.conf sample described before). emerging process is ok.

Does it can be related to symlink /usr/armv7a-hardfloat-linux-gnueabi/sys-include that points to native /usr/include?
Or problem related to make.conf portage environment variables? Ivee tried both variants of variables described (for CHOST and for PAZ00 ) at make.conf sample

Help me plz, i spent so much time on this, reinstalled many times toolchain, rootfs, and still nothing. Everytime same thing.
Thanks in advance.

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


Joined: 05 Jul 2003
Posts: 47163
Location: 56N 3W

PostPosted: Sun Oct 09, 2016 9:41 pm    Post subject: Reply with quote

n05ph3r42,

When you
Code:
chroot /usr/armv7a-hardfloat-linux-gnueabi

Your /etc/portage, inside the chroot is still set up for cross compiling.
In particular. make.conf will need to be reviewed.
Code:
CBUILD="x86_64-pc-linux-gnu"
HOSTCC="x86_64-pc-linux-gnu-gcc"
will be incorrect.

Code:
MAKEOPTS="-j5"
will be sub optimal. You have a single arm core emulated in software.

Code:
ROOT="/usr/${CHOST}/"
needs to be
Code:
ROOT="/"

There will be other things.

You probably need to run gcc-config too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Mon Oct 10, 2016 6:24 am    Post subject: Reply with quote

NeddySeagoon,
Hello,
As You can understand from my first post, i switching sections described at make.conf example (CHOST to PAZ00) when chrooting in. And yes, i forgot to move
Code:

CBUILD="x86_64-pc-linux-gnu"
HOSTCC="x86_64-pc-linux-gnu-gcc"

to "ENV 4 CHOST SECTION" in my make.conf example.
I mean, i did that in my morking make.conf. These lines is not present in make.conf for chrootfs (PAZ00 section), they are in make.conf (for CHOST section) when using it if not chrooted (in native environment). Otherwise i think, will get message that c compiler cannot create executables.

As for ROOT variable - i define it in commandline before calling emerge for rootfs that is not at /usr/{CHOST} this way:
Code:

cd to rootfs
#cd /root/paz00_rootfs
run emerge with "ROOT = /root/paz00_rootfs"
#ROOT=$PWD armv7a-hardfloat-linux-gnueabi-emerge @system --keep-going -avt
Back to top
View user's profile Send private message
cwr
Veteran
Veteran


Joined: 17 Dec 2005
Posts: 1969

PostPosted: Mon Oct 10, 2016 9:29 am    Post subject: Reply with quote

For the BeagleBone Black I have the following changes in make.conf:
Code:

# BeagleBone Black flags.
ACCEPT_KEYWORDS="arm ~arm"
CFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard"
MAKEOPTS="-j2"
CHOST="armv7a-hardfloat-linux-gnueabi"
CXXFLAGS="${CFLAGS}"

USE="arm bindist make-symlinks minimal X zlib -doc"

VIDEO_CARDS="dummy fbdev modesetting omap omapfb v4l"


Most stuff can be cross-compiled under a chroot, but eg. python has to be compiled
natively. I just let it run overnight.

Will
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47163
Location: 56N 3W

PostPosted: Mon Oct 10, 2016 9:42 am    Post subject: Reply with quote

cwr,

Python pure cross compiled for me on amd64 to arm64. I think that's as a result of EAPI 6.
Lots of things that were broken seem to be better.

Perl is still broken because of its build system and gcc was a problem too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Mon Oct 10, 2016 6:29 pm    Post subject: Reply with quote

Well, i try to explain other way.
The problem is not in python. Python works nice (i think).
The problem, i think, is in include path for directory with modules, used by emerge. They are broken by cross-compiler-toolchain, or bad env vars used by it, i think.
All errors raised when i chrootin in any of these rootfs, are related to emerge, (and deeper, python tries to use modules related to emerge and cant find them) ,
so when i call emerge in chroot i got errors "module not found", such as
Code:

 ImportError: No module named 'portage'.
 


The other side is that i use two make.conf files (actually 3, but 2&3 both for paz00 rootfs, these files differs by CBUILD HOSTCC & ELIBC - one have these, other not, and sure, makeopts)

1) make.conf for CHOST when calling armv7a-hardfloat-linux-gnueabi-emerge in native environment for rootfs ( /usr/CHOST )that im trying to build from scratch:
Code:

#MAKE.CONF FOR ROOTFS@/usr/CHOST  TO COMPILE AT HOSTCC native environment
CHOST="armv7a-hardfloat-linux-gnueabi"
ARCH="arm"

CFLAGS="-O2 -pipe -fomit-frame-pointer -ftree-vectorize -fno-stack-protector -U_FORTIFY_SOURCE -march=armv7-a -mtune=cortex-a9 -mfpu=vfpv3-d16 -mfloat-abi=hard"
CXXFLAGS="${CFLAGS}"

MAKEOPTS="-j5"

ACCEPT_KEYWORDS="arm"
USE="${ARCH} -acl fbdev -pam minimal threads -xattr"
FEATURES="collision-protect buildpkg noman noinfo nodoc parallel-fetch\
 parallel-install sandbox sfperms strict unknown-features-warn unmerge-logs\
 unmerge-orphans userfetch"

# ENV VARS 4 CHOST
CBUILD="x86_64-pc-linux-gnu"
HOSTCC="x86_64-pc-linux-gnu-gcc"
ELIBC="glibc"
ROOT="/usr/${CHOST}/"
PKGDIR="${ROOT}packages/"
PORTAGE_TMPDIR="${ROOT}tmp/"
PKG_CONFIG_PATH="${ROOT}usr/lib/pkgconfig/"
# !ENV VARS 4 CHOST

VIDEO_CARDS="fbdev tegra"

GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles/"
LINGUAS="en ru"
L10N="en ru"



2) make.conf for ROOTFS@/root/PAZ00 when calling armv7a-hardfloat-linux-gnueabi-emerge in native environment for rootfs (/root/PAZ00 ) that contains extracted armv7a-hf stage tarball,
defining ROOT=PWD$, when current dir is /root/PAZ00
Code:

# MAKE.CONF FOR ROOTFS@/root/PAZ00  TO COMPILE AT HOSTCC native environment
#
# DEFINING ROOT=PWD$ when PWD is /root/PAZ00 before calling emerge:
# /root/PAZ00#ROOT=PWD$ armv7a-hardfloat-linux-gnueabi-emerge @system

CHOST="armv7a-hardfloat-linux-gnueabi"
ARCH="arm"

CFLAGS="-O2 -pipe -fomit-frame-pointer -ftree-vectorize -fno-stack-protector -U_FORTIFY_SOURCE -march=armv7-a -mtune=cortex-a9 -mfpu=vfpv3-d16 -mfloat-abi=hard"
CXXFLAGS="${CFLAGS}"

MAKEOPTS="-j5"

ACCEPT_KEYWORDS="arm"
USE="${ARCH} -acl fbdev -pam minimal threads -xattr"
FEATURES="collision-protect buildpkg noman noinfo nodoc parallel-fetch\
 parallel-install sandbox sfperms strict unknown-features-warn unmerge-logs\
 unmerge-orphans userfetch"

# ENV 4 PAZ00 ROOTFS
CBUILD="x86_64-pc-linux-gnu"
HOSTCC="x86_64-pc-linux-gnu-gcc"
ELIBC="glibc"
ROOT=""
PORTDIR="${ROOT}/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"
PKG_CONFIG_PATH="${ROOT}/usr/lib/pkgconfig"
PORTAGE_TMPDIR="${ROOT}/tmp"
# ENV 4 PAZ00 ROOTFS

VIDEO_CARDS="fbdev tegra"

GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles/"
LINGUAS="en ru"
L10N="en ru"


3). make.conf for ROOTFS@/root/PAZ00 when chrooted in (contains extracted armv7a-hf stage tarball)
Code:

# MAKE.CONF FOR ROOTFS@/root/PAZ00  TO COMPILE WHEN CHROOTED IN
# calling emerge common way : emerge @system --update --deep --withb-deps=y --newuse --keep-going

CHOST="armv7a-hardfloat-linux-gnueabi"
ARCH="arm"

CFLAGS="-O2 -pipe -fomit-frame-pointer -ftree-vectorize -fno-stack-protector -U_FORTIFY_SOURCE -march=armv7-a -mtune=cortex-a9 -mfpu=vfpv3-d16 -mfloat-abi=hard"
CXXFLAGS="${CFLAGS}"

MAKEOPTS="-j3"

ACCEPT_KEYWORDS="arm"
USE="${ARCH} -acl fbdev -pam minimal threads -xattr"
FEATURES="collision-protect buildpkg noman noinfo nodoc parallel-fetch\
 parallel-install sandbox sfperms strict unknown-features-warn unmerge-logs\
 unmerge-orphans userfetch"

# ENV 4 PAZ00 ROOTFS WHEN CHROOTED IN
ROOT=""
PORTDIR="${ROOT}/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"
PKG_CONFIG_PATH="${ROOT}/usr/lib/pkgconfig"
PORTAGE_TMPDIR="${ROOT}/tmp"
# ENV 4 PAZ00 ROOTFS

VIDEO_CARDS="fbdev tegra"

GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles/"
LINGUAS="en ru"
L10N="en ru"
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Mon Oct 10, 2016 6:32 pm    Post subject: Reply with quote

P.S. im most interested in case with building rootfs from scrastch to achieve minimal fastest system. This is make.conf #1 for rootfs at /usr/CHOST
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Thu Oct 13, 2016 4:45 pm    Post subject: Reply with quote

Found that site-packages was absolutely empty for python2.7 as well as for python3.4.
Why this folders were empty, can anybody explain? I just want to know what i did wrong.

I've copied those dirs from stage tarball and now emerging any package gives another lib error:

libgcc_s.so.1: cannot open shared object file: No such file or directory

Code:

ace / # gcc-config -l
 [1] armv7a-hardfloat-linux-gnueabi-4.9.3 *
ace / # gcc-config -E
export PATH="/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.9.3:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.9.3"
export GCC_SPECS=""
ace / # ls usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.9.3 | grep libgcc_s.so.1
libgcc_s.so.1
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Fri Oct 14, 2016 9:36 am    Post subject: Reply with quote

Code:

#ldconfig

when chrooted into CHOST solved the problem. Missed it. RTFM!

Close topic. Thanks all for your interest.

P.S. why site-packages was empty is still mystery for me.
Back to top
View user's profile Send private message
xaviermiller
Bodhisattva
Bodhisattva


Joined: 23 Jul 2004
Posts: 8623
Location: ~Brussels - Belgique

PostPosted: Fri Oct 14, 2016 9:43 am    Post subject: Reply with quote

Hi!

Take a look at ${CHROOT}/usr/lib64.

I observed Perl and Python packages are not cross-compiled in the right directory. But I didn't opened a bug report yet.
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
n05ph3r42
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jul 2016
Posts: 120

PostPosted: Fri Oct 14, 2016 11:16 am    Post subject: Reply with quote

Ouch!
Got another issue now. When package is installing after compiling in chrooted environment, got list of bad syscalls by qemu:
Code:

chmod a+x '/tmp/portage/sys-devel/libtool-2.4.6/image//usr/share/libtool/configure'
make[3]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
make[2]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
make[1]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
>>> Completed installing libtool-2.4.6 into /tmp/portage/sys-devel/libtool-2.4.6/image/

 * Final size of build directory: 14104 KiB
 * Final size of installed tree: 3976 KiB

qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
ecompressdir: bzip2 -9 /usr/share/doc
ecompressdir: bzip2 -9 /usr/share/info
ecompressdir: bzip2 -9 /usr/share/man
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
>>> Done.

>>> Installing (5 of 5) sys-devel/libtool-2.4.6::gentoo
 * Removing /usr/share/man
 * Removing /usr/share/info
 * Removing /usr/share/doc
qemu: Unsupported syscall: 373

>>> Recording sys-devel/libtool in "world" favorites file...
>>> Auto-cleaning packages...
Back to top
View user's profile Send private message
Latrina
n00b
n00b


Joined: 13 Aug 2017
Posts: 34
Location: Cambridge, UK

PostPosted: Sun Oct 15, 2017 10:45 am    Post subject: Reply with quote

n05ph3r42 wrote:
Ouch!
Got another issue now. When package is installing after compiling in chrooted environment, got list of bad syscalls by qemu:
Code:

chmod a+x '/tmp/portage/sys-devel/libtool-2.4.6/image//usr/share/libtool/configure'
make[3]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
make[2]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
make[1]: Leaving directory '/tmp/portage/sys-devel/libtool-2.4.6/work/libtool-2.4.6'
>>> Completed installing libtool-2.4.6 into /tmp/portage/sys-devel/libtool-2.4.6/image/

 * Final size of build directory: 14104 KiB
 * Final size of installed tree: 3976 KiB

qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
ecompressdir: bzip2 -9 /usr/share/doc
ecompressdir: bzip2 -9 /usr/share/info
ecompressdir: bzip2 -9 /usr/share/man
qemu: Unsupported syscall: 383
scanelf: seccomp_load failed: Bad address
>>> Done.

>>> Installing (5 of 5) sys-devel/libtool-2.4.6::gentoo
 * Removing /usr/share/man
 * Removing /usr/share/info
 * Removing /usr/share/doc
qemu: Unsupported syscall: 373

>>> Recording sys-devel/libtool in "world" favorites file...
>>> Auto-cleaning packages...


Perhaps a little late but hopefully my finding will help someone else in the future.

I might be mistaken but as far as I understood seccomp() is not supported by qemu-user for arm.

As long as the packages do get installed you should be fine with it, and as advised by the #gentoo-embedded community, you could get rid of the seccomp() related error messages in emerge by recompiling app-misc/pax-utils without seccomp.

Code:

echo "app-misc/pax-utils -seccomp" >> /etc/portage/package.use/app-misc


and update @world after that.

If you want seccomp() syscall in your kernel and on the native hardware, make sure to remove what mentioned above and updating @world afterward.
_________________
USE="-systemd"


Last edited by Latrina on Sun Oct 15, 2017 8:19 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 47163
Location: 56N 3W

PostPosted: Sun Oct 15, 2017 11:28 am    Post subject: Reply with quote

Moved from Portage & Programming to Gentoo on ARM.

Our shiny new ARM forum.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 16512

PostPosted: Sun Oct 15, 2017 6:33 pm    Post subject: Reply with quote

Latrina wrote:
Code:
echo "app-misc/pax-utils without -seccomp" >> /etc/portage/package.use/app-misc
Package app-misc/pax-utils does not include without in IUSE. There is no need to set the USE=without flag.
Back to top
View user's profile Send private message
Latrina
n00b
n00b


Joined: 13 Aug 2017
Posts: 34
Location: Cambridge, UK

PostPosted: Sun Oct 15, 2017 8:19 pm    Post subject: Reply with quote

Hu wrote:
Latrina wrote:
Code:
echo "app-misc/pax-utils without -seccomp" >> /etc/portage/package.use/app-misc
Package app-misc/pax-utils does not include without in IUSE. There is no need to set the USE=without flag.


That was a typo. My bad.
_________________
USE="-systemd"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM 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