| View previous topic :: View next topic |
| Author |
Message |
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
 Posted: Mon Jul 16, 2018 1:06 pm Post subject: Nothing builds - [RESOLVED] |
 |
|
Hi,
I'm sure this has to do with either the new profiles or now compilers, but somehow, I cannot compile anything.
| Code: | gcc-config -l
[1] i686-w64-mingw32-7.3.0 *
[2] x86_64-pc-linux-gnu-6.4.0
[3] x86_64-pc-linux-gnu-7.3.0 *
[4] x86_64-w64-mingw32-6.3.0 * |
Whichever compiler I select, I get the same error:
. /etc/profile
emerge -1 sys-devel/libtool
| Code: | [...]
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/sys-devel/libtool-2.4.6-r3/work/libtool-2.4.6':
configure: error: C compiler cannot create executables
gcc version 7.3.0 (Gentoo 7.3.0-r3 p1.4)
configure:3882: $? = 0
configure:3871: x86_64-pc-linux-gnu-gcc -V >&5
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-V'
x86_64-pc-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:3882: $? = 1
configure:3871: x86_64-pc-linux-gnu-gcc -qversion >&5
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
x86_64-pc-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:3882: $? = 1
configure:3902: checking whether the C compiler works
configure:3924: x86_64-pc-linux-gnu-gcc -Os -march=native -pipe -Wl,-O1 -Wl,--as-needed conftest.c >&5
collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped
compilation terminated.
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o: bad reloc symbol index (0x696e69 >= 0x13) for offset 0x635f6362696
c5f5f in section `rela.text'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/crti.o: bad reloc symbol index (0x4241545f >= 0xb) for offset 0x464f5f4c414
24f4c in section `la.init'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o symbol number 0 references nonexistent SHT_SYMTAB_SHNDX section
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: can not read symbols: Bad value
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: .eh_frame/.stab edit: Bad value
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: warning: cannot find entry symbol _start; defaulting to 00000000000003d0
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.interp' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `tab' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.gnu.hash' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.dynsym' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.dynstr' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.gnu.version' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.gnu.version_r' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.rela.dyn' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.init' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.plt' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.plt.got' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.text' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `rela.text' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `la.init' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.fini' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `ext' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `rela.eh_frame' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.eh_frame' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.init_array' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.fini_array' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.dynamic' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.got' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.got.plt' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `.data' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `ame' not in segment
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: a.out: warning: allocated section `t' not in segment
configure:3928: $? = 1
configure:3966: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU Libtool"
| #define PACKAGE_TARNAME "libtool"
| #define PACKAGE_VERSION "2.4.6"
| #define PACKAGE_STRING "GNU Libtool 2.4.6"
| #define PACKAGE_BUGREPORT "bug-libtool@gnu.org"
| #define PACKAGE_URL "http://www.gnu.org/software/libtool/"
| #define PACKAGE "libtool"
| #define VERSION "2.4.6"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3971: error: in `/var/tmp/portage/sys-devel/libtool-2.4.6-r3/work/libtool-2.4.6':
configure:3973: error: C compiler cannot create executables |
Thanks for taking the time to read this,
What is the correct way to get things working again?
Thanks
Mod edit: [code] tags added for clarity. — JRG
Last edited by Progman3K on Fri Aug 10, 2018 5:54 pm; edited 2 times in total |
|
| Back to top |
|
 |
John R. Graham
Administrator
Joined: 08 Mar 2005
Posts: 10589
Location: Somewhere over Atlanta, Georgia
|
| Posted: Mon Jul 16, 2018 1:09 pm Post subject: |
|
|
This is often an error in CFLAGS in make.conf, so much so that it has its own FAQ entry. Post your make.conf if you'd like help troubleshooting.
Edit: With ld segfaulting, this may not be as simple as that. Post your make.conf anyways, though.
- John
_________________
I can confirm that I have received between 0 and 499 National Security Letters.
Last edited by John R. Graham on Mon Jul 16, 2018 1:12 pm; edited 1 time in total |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30917
Location: here
|
| Posted: Mon Jul 16, 2018 1:11 pm Post subject: |
|
|
Did it work before? What have you done in the meantime?
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
joanandk
Apprentice
Joined: 12 Feb 2017
Posts: 169
|
| Posted: Mon Jul 16, 2018 1:14 pm Post subject: Re: Nothing builds |
|
|
| Progman3K wrote: | | but somehow, I cannot compile anything. |
DId you do an after the change to GCC 7.3?
BR |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Mon Jul 16, 2018 1:19 pm Post subject: |
|
|
The preceding error-log was the result of emerge -1 sys-devel/libtool
Contents of /etc/portage/make.conf
| Quote: | CFLAGS="-Os -march=native -pipe"
CXXFLAGS="${CFLAGS}"
# 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"
CPU_FLAGS_X86="avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="abi_x86_32 avx alsa bash-completion dvd dvdr \
-fortran fuse git \
mmx mmxext modemmanager mtp \
nautilus networkmanager \
popcnt \
-sanitize samba sse sse2 sse3 sse4_1 sse4_2 ssse3 ssh \
threads unicode user-session -vtv"
PORTDIR="/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"
#VIDEO_CARDS="nvidia"
VIDEO_CARDS="nouveau"
#MAKEOPTS="-j9"
MAKEOPTS="-j1"
GRUB_PLATFORMS="efi-64"
PORTDIR_OVERLAY="/usr/local/crossdev-overlay"
ACCEPT_LICENSE="*"
FEATURES="nostrip installsources"
source /var/lib/layman/make.conf
|
Everything was building and compiling until the last update, I believe |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54244
Location: 56N 3W
|
| Posted: Mon Jul 16, 2018 4:51 pm Post subject: |
|
|
Progman3K,
It appears that your linker is broken.
Does show more that one?
Try a different one.
If that fails too, try the gold linker.
The idea is to get you going enough to fix your system.
Beware the gold linker for long term use, as some things fail to link with it anyway.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Mon Jul 16, 2018 6:26 pm Post subject: |
|
|
binutils-config -l | Quote: | [1] armv7a-hardfloat-linux-gnueabihf-2.29.1 * (blue)
[2] armv7a-hardfloat-linux-gnueabihf-2.30
[3] i686-w64-mingw32-2.30 * (blue)
[4] x86_64-pc-linux-gnu-2.29.1 * (green)
[5] x86_64-pc-linux-gnu-2.30
[6] x86_64-w64-mingw32-2.28 * (blue)
|
Oddly, it still lists the cross-compiler linker I thought was removed when I unmerged the corresponding arm compiler...
Could that be the source of the problem?
[EDIT] Selecting #5 (x86_64-pc-linux-gnu-2.30) instead of #4 (x86_64-pc-linux-gnu-2.29.1) still gives an error, albeit a different one, so still no joy
| Quote: | /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o: bad reloc symbol index (0x696e69 >= 0x13) for offset 0x635f6362696c5f5f in section `rela.text'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
/usr/bin/xmkmf: line 53: 14275 Aborted (core dumped) imake $imake_defines $args
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54244
Location: 56N 3W
|
| Posted: Mon Jul 16, 2018 7:39 pm Post subject: |
|
|
Progman3K,
Did you do the gcc-4.x to 5.x migration as per the news item?
What about the /13.0/ to /17.0/ profile update along with gcc-6.x going stable?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Mon Jul 16, 2018 7:52 pm Post subject: |
|
|
| NeddySeagoon wrote: | Progman3K,
Did you do the gcc-4.x to 5.x migration as per the news item?
What about the /13.0/ to /17.0/ profile update along with gcc-6.x going stable? |
I'm going to go ahead and say no, I probably didn't. According to my (vague) memories of updating the compiler, I believed (at the time) that the additional procedure was not mandatory.
I'll look in portage's log, to see what steps it recommended, unless someone has a link the appropriate article.
Thanks again |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Mon Jul 16, 2018 8:22 pm Post subject: |
|
|
| NeddySeagoon wrote: | Did you do the gcc-4.x to 5.x migration as per the news item?
What about the /13.0/ to /17.0/ profile update along with gcc-6.x going stable? |
| Progman3K wrote: | | I'll look in portage's log, to see what steps it recommended, unless someone has a link the appropriate article. |
Progman3K ... see: 2015-10-22-gcc-5-new-c++11-abi and 2017-11-30-new-17-profiles.
best ... khay |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Tue Jul 17, 2018 12:00 pm Post subject: |
|
|
All measures recommended by the advisory bulletins fail, I fear I may have let things slip too long and now there is no easy way to correct the situation:
Emerging libtool fails, revdep-rebuild fails because of conflicts but even if it didn't I suspect it would fail during linking anyway.
I'm imagining some possible options:
- Install the gold linker and try to build a compiler-toolset. (Is that workable?)
- Extract a subset (compiler, linker, binutils) of a stage3 archive on top of the installation.
Unless there are better, simpler possibilities |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Tue Jul 17, 2018 12:47 pm Post subject: |
|
|
| Progman3K wrote: | | Unless there are better, simpler possibilities |
Progman3K ... one option is to grab binpkg for the toolchain from a binhost and unpack these into /
| Code: | | # tar -xpf --xattrs-include='*.*' --numeric-owner binpkg.tbz2 -C / |
... and then rebuild the toolchain, and whaterver else is required to get to 17.0
HTH & best ... khay |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Tue Jul 17, 2018 6:51 pm Post subject: |
|
|
I executed the following command
(I manually deleted ld first to make sure the extraction would restore it. It did.)
| Code: | tar --xattrs-include='*.*' --numeric-owner -xpf /binutils-2.30-r2.tbz2 -C /
tar --xattrs-include='*.*' --numeric-owner -xpf /gcc-7.3.0-r3.tbz2 -C /
tar --xattrs-include='*.*' --numeric-owner -xpf /binutils-config-5-r4.tbz2 -C / |
gcc-config -l
| Quote: | * Python seems to be broken, attempting to locate CHOST ourselves ...
[1] i686-w64-mingw32-7.3.0 * (blue)
[2] x86_64-pc-linux-gnu-6.4.0
[3] x86_64-pc-linux-gnu-7.3.0 * (green)
[4] x86_64-w64-mingw32-6.3.0 * (blue) |
binutils-config -l
| Quote: | /usr/bin/binutils-config: line 373: portageq: command not found
* binutils-config: unable to locate a profile for target: |
I created a file called main.cpp
| Quote: |
#include <stdio.h>
int main( void ) {
return 0;
} |
tried to compile the file
g++ main.cpp
| Quote: | /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o: bad reloc symbol index (0x696e69 >= 0x13) for offset 0x635f6362696c5f5f in section `rela.text'
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/Scrt1.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status |
Things seem to be getting worse...
Might have to reinstall from scratch |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Wed Aug 08, 2018 4:11 pm Post subject: There really does seem to be something wrong with the hw |
|
|
After running memtest on the machine and detecting that one of the RAM modules had a stuck-bit, and replacing it, everything seemed to be dependable.
But after days of effort testing and re-installing everything, I got this message in dmesg:
| Quote: | WARNING: CPU: 1 PID: 260 at arch/x86/kernel/check.c:142 check_for_bios_corruption+0x9b/0xe0
Modules linked in: x86_pkg_temp_thermal
CPU: 1 PID: 260 Comm: kworker/1:1 Not tainted 4.14.52-gentoo #3
Hardware name: Acer Veriton M4618G/Veriton M4610G, BIOS P01-A2 07/20/2011
Workqueue: events check_corruption
task: ffff943e6f8a5e80 task.stack: ffff9b71c1bac000
RIP: 0010:check_for_bios_corruption+0x9b/0xe0
RSP: 0018:ffff9b71c1bafe60 EFLAGS: 00010286
RAX: 0000000000000028 RBX: ffff943b40010000 RCX: 0000000000000000
RDX: ffff943e7e25d0d0 RSI: ffff943e7e2554d8 RDI: ffff943e7e2554d8
RBP: 0000000000000000 R08: 00000000000002a9 R09: 0000000000aaaaaa
R10: 0000000000001000 R11: 00000000ffffffff R12: ffffffff85e037d0
R13: 0000000000000001 R14: 0000000080000000 R15: ffffffff80000000
FS: 0000000000000000(0000) GS:ffff943e7e240000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bf0c6fba50 CR3: 00000001c100a001 CR4: 00000000000606e0
Call Trace:
check_corruption+0x5/0x30
process_one_work+0x1c9/0x3c0
worker_thread+0x26/0x3c0
? trace_event_raw_event_workqueue_execute_start+0x80/0x80
kthread+0x114/0x130
? kthread_create_on_node+0x40/0x40
? call_usermodehelper_exec_async+0x111/0x140
ret_from_fork+0x35/0x40
Code: c0 75 0c 5b 5d 41 5c 41 5d 41 5e 41 5f c3 c3 80 3d cb c3 2b 01 00 75 eb 48 c7 c7 78 b0 5a 85 c6 05 bb c3 2b 01 01 e8 cb a7 05 00 <0f> 0b eb d4 48 89 da 4c 01 f2 72 2a 4c 89 f8 48 2b 05 57 9d 1f |
So, is this another bad RAM module, or is there some other bit of hardware that can be causing this? |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Wed Aug 08, 2018 4:38 pm Post subject: Re: There really does seem to be something wrong with the hw |
|
|
| Progman3K wrote: | | So, is this another bad RAM module, or is there some other bit of hardware that can be causing this? |
Progman3K ... I don't think so, CONFIG_X86_CHECK_BIOS_CORRUPTION is the cause but it doesn't necessarily mean that memory is corrupt, only that the code faults. Can we see what comes directly before the "WARNING"?
best ... khay |
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Wed Aug 08, 2018 5:36 pm Post subject: |
|
|
Hi Khayyam!
It happens within a few minutes from cold-boot, but there doesn't seem to be any preceding cause...
Here's the dmesg output:
https://pastebin.com/qKHVuAm2
EDIT: I've rebooted the machine 3 times now, and all 3 times, it issued the same error message about 62 seconds after the boot. I suspect this is the frequency at which the check is done (~60 seconds) and that once it detects a corruption, it does not warn anymore until you reboot. The first two times, I booted kernel 4.14.52, the third time, I booted kernel 4.14.61. All behave the same. |
|
| Back to top |
|
|
Yamakuzure
Advocate
Joined: 21 Jun 2006
Posts: 2284
Location: Adendorf, Germany
|
| Posted: Thu Aug 09, 2018 8:00 am Post subject: |
|
|
May this thread be of assistance?
_________________
Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
| Back to top |
|
|
Progman3K
l33t
Joined: 03 Jan 2004
Posts: 773
|
| Posted: Thu Aug 09, 2018 12:07 pm Post subject: |
|
|
Khayyam & Yamakuzure,
Thanks, that clears up the question of where/why for the BIOS-memory message.
I guess the only question I have left is, do I mark this thread as resolved?
Is it reasonable to assume that the linker/other-files corruption and loss of the boot partition were all caused by a bad RAM module? I suppose only time will tell. |
|
| Back to top |
|
|
Yamakuzure
Advocate
Joined: 21 Jun 2006
Posts: 2284
Location: Adendorf, Germany
|
| Posted: Fri Aug 10, 2018 7:20 am Post subject: |
|
|
| Progman3K wrote: | | I guess the only question I have left is, do I mark this thread as resolved? |
Well, your initial problem was: "Nothing builds" and that is resolved, right? So yes, I'd mark this thread as [resolved]. 
_________________
Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
| Back to top |
|
|
|
Portage & Programming
