Installing Gentoo on an old laptop. What does he want from me?

Question

linux

After many answers to this question, I decided to give Gentoo a try.
Because can be assembled with optimization for the percentage (which is clearly not superfluous for P3 @ 700) and know exactly what is and what is not.
I uploaded a mini-image to the flash drive (sd and dvd did not start), launched the mini, downloaded stage3, unpacked it, chrooted zero, and, when I tried to download the kernel

(chroot) livecd / # emerge --ask sys-kernel/gentoo-sources

Got such an error

spoiler

(chroot) livecd / # emerge --ask sys-kernel/gentoo-sources
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] sys-devel/bc-1.06.95-r1 USE="readline -libedit -static"
[ebuild N ] sys-kernel/gentoo-sources-4.1.15-r1 USE="-build -experimental -kdbus -symlink"
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) sys-devel/bc-1.06.95-r1::gentoo
* bc-1.06.95.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking bc-1.06.95.tar.bz2 to /var/tmp/portage/sys-devel/bc-1.06.95-r1/work
>>> Source unpacked in /var/tmp/portage/sys-devel/bc-1.06.95-r1/work
>>> Preparing source in /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95 ...
* Applying bc-1.06.95-void_uninitialized.patch ... [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95 ...
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib --with-readline --without-libedit
checking for a BSD-compatible install... /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... configure: error: cannot find output from flex; giving up
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95/config.log
econf failed
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95 ...
make -j2 AR=i686-pc-linux-gnu-ar
make: *** No targets specified and no makefile found. Stop.
emake failed
* ERROR: sys-devel/bc-1.06.95-r1::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 133: Called src_compile
* environment, line 2193: Called die
* The specific snippet of code:
* emake AR="$(tc-getAR)" || die
*
* If you need support, post the output of `emerge --info '=sys-devel/bc-1.06.95-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/bc-1.06.95-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-devel/bc-1.06.95-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/bc-1.06.95-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95'
* S: '/var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95'
>>> Failed to emerge sys-devel/bc-1.06.95-r1, Log file:
>>> '/var/tmp/portage/sys-devel/bc-1.06.95-r1/temp/build.log'
* Messages for package sys-devel/bc-1.06.95-r1:
* ERROR: sys-devel/bc-1.06.95-r1::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 133: Called src_compile
* environment, line 2193: Called die
* The specific snippet of code:
* emake AR="$(tc-getAR)" || die
*
* If you need support, post the output of `emerge --info '=sys-devel/bc-1.06.95-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/bc-1.06.95-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-devel/bc-1.06.95-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/bc-1.06.95-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95'
* S: '/var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95'

In google, this is usually handled when building PHP5 and missing Flex
, and I have both lex and flex .......
an error, as I understand it. this

checking lex output file root... configure: error: cannot find output from flex; giving up

But what she wants from me ... I don't understand
... which video driver is best for me

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility AGP 2x Series (rev 64)

And how can he do KDE2 or 3 on the 3.10 kernel (the kernel is still supported by gentoo). otherwise he wants to stick me gentoo-sources-4.1.15-r1
This. there are no words...

spoiler

_____________________________________________________________________________________________________________________________
Перезагрузил комп с недоустановленной гентой (на другом , (с которого цеплялся по ssh) сменил систему)
....
И тут началось веселье : он перестал загружаться (зависал на загрузке ядра (с флешки, когда стартовал)......
Перекатал флешку (закатал образ снова) .... Загрузился... Все норм... но ssh меня перестал пускать... покапался в настройках (что - то типо premitrootlogin yes сделал, и еще пару... (не затрагивающих сеть)).... и тут он меня начал пускать... я принял сертификат (ну, когда в первый раз цепляешься) ввел пароль и СРАЗУ же получил Broken pipe
....
Менял порты, адреса, пользователей, .... ...... ... ПРОВОДА поменял... что ему нужно? (цеплять пробовал с двух машин в одной сети (debian 8.3 kde через ssh и win10 через putty) обрыв соед-я.... что за фигня... форматил диск (вдруг он своп цепял, все менял... ошибка... как с ней бороться, и откуда она взялась? до этого все ж с пол-пинка работало...
_______________________________________________________________________________________________________________________________
Еще перезагрузил.... в /etc/ssh/sshd_config на п3 поставил
Port 2233
Listenaddress 192.168.1.15 #Desctop address
TcpKeepalive yes
может еще что-тo
компьютер ответил
[email protected]:~$ ssh -p 2233 [email protected]
ssh: connect to host 192.168.1.2 port 2233: Connection refused
(us -- новый пользователь) (с рутом тоже самое, и с другими портами тоже)
при этом
[email protected]:~$ ping -s 55000 192.168.1.2
работает без потерь пакетов 2 мин (дальше не вижу смысла)
что за хрень?
__________________________________________________________________________________________________________________________________
Прописал на ноуте (где сервер ссш не хочет работать)
ssh [email protected] -p2233
(за ранее дописав ListenAddress localhost:2233)
Соед-е прошло..... принял сертификат .... ввел пароль ... и...
packet_write_wait: Connection to 127.0.0.1: Brocken pipe
Это что за прикол?
(очевидно с кампьютера я получал cоnnection refuced из-за какого-то фиревола, значит буду работать со стандартным портом)
Заработало....
перекатал флешку, загрузился. создал пользователя с хардкорным (qawsedrf) паролем и такой же дал руту.
заходил на пользователя....
пустило...

Answer 1

Go to /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95 and read config.log, it says in detail what happened. If you don't understand, post it and read it together.

Answer 2

The log should be looked at to which it refers. Configure tried to do something with flex, did not get the expected result and wrapped the bots. As a rule, configure does not shine with intellect, so it is necessary to look at the log