| View previous topic :: View next topic |
| Author |
Message |
Maquis196
n00b
Joined: 02 Apr 2003
Posts: 62
Location: London
|
 Posted: Sun May 27, 2018 10:53 pm Post subject: Have an issue with crossdev perhaps Alpha platform [SOLVED] |
 |
|
So basically an older version of the usual crossdev requirements compiled fine (but from a while ago now). So after trying to get to the current latest stable, most things worked but alas glibc doesn't.
so I run;
| Code: |
crossdev -S -t alpha-unknown-linux-gnu --k 4.16.9 --g 6.4.0-r1 --l 2.25-r11 --b 2.29.1-r1
|
Now, only glibc fails (have yet to try it on the my actual alpha box, been compiling gcc all day), with;
| Code: |
Calculating dependencies... done!
[ebuild R ] cross-alpha-unknown-linux-gnu/glibc-2.25-r11:2.2::crossdev USE="rpc -audit -caps -debug -gd -hardened -headers-only* -multilib -nscd -profile (-selinux) -suid -systemtap -vanilla" 0 KiB
|
| Code: |
checking for broken __attribute__((alias()))... yes
configure: error: working alias attribute support required
* ERROR: cross-alpha-unknown-linux-gnu/glibc-2.25-r11::crossdev failed (configure phase):
* failed to configure glibc
*
* Call stack:
* ebuild.sh, line 124: Called src_configure
* environment, line 3109: Called toolchain-glibc_src_configure
* environment, line 4436: Called foreach_abi 'toolchain-glibc_do_src_configure'
* environment, line 1280: Called toolchain-glibc_do_src_configure
* environment, line 4119: Called glibc_do_configure 'nptl'
* environment, line 1879: Called die
* The specific snippet of code:
* "$@" || die "failed to configure glibc";
|
I can't seem to find much on this, the host has 2.25-r11 installed as well (amd64 kvm client basically). So is this a DEC thing? should I wait until I've got it working on the alpha itself first? Like I said though, the older version I had was working;
| Code: |
crossdev --stable -t alpha-unknown-linux-gnu -k 4.0.0 -g 4.8.4 -l 2.19 -b 2.24
|
but as you can see... ancient 
Last edited by Maquis196 on Mon May 28, 2018 3:58 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54577
Location: 56N 3W
|
| Posted: Mon May 28, 2018 12:57 pm Post subject: |
|
|
Maquis196,
configure leaves a configure.log file in the build location somewhere.
Please put it onto a pastebin site. Its far too big for a post.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Maquis196
n00b
Joined: 02 Apr 2003
Posts: 62
Location: London
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54577
Location: 56N 3W
|
| Posted: Mon May 28, 2018 2:21 pm Post subject: |
|
|
Maquis196,
Let me try to add a DEC Alpha cross toolchain to my collection.
The error doesn't mean anything to me, so I'll try to reproduce it here.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54577
Location: 56N 3W
|
| Posted: Mon May 28, 2018 3:09 pm Post subject: |
|
|
Maquis196,
Well, it worked fol me. I did have to switch back to the bfd linker though.
That's the default anyway.
| Code: | # less /var/log/portage//cross-alpha-unknown-linux-gnu-glibc-headers.log
NeddySeagoon_Static ~ # binutils-config --linker ld.bfd
* Setting default linker to ld.bfd for x86_64-pc-linux-gnu-2.30 ... [ ok ]
NeddySeagoon_Static ~ # crossdev -S -t alpha-unknown-linux-gnu --k 4.16.9 --g 6.4.0-r1 --l 2.25-r11 --b 2.29.1-r1
-
* crossdev version: 20180508
* Host Portage ARCH: amd64
* Target Portage ARCH: alpha
* Target System: alpha-unknown-linux-gnu
* Stage: 4 (C/C++ compiler)
* USE=multilib: no
* ABIs: default
* binutils: binutils-2.29.1-r1
* gcc: gcc-6.4.0-r1
* headers: linux-headers-4.16.9
* libc: glibc-2.25-r11
* CROSSDEV_OVERLAY: /usr/local/gentoo-static
* PORT_LOGDIR: /var/log/portage/
* PORTAGE_CONFIGROOT: /
* Portage flags:
* leaving sys-devel/binutils in /usr/local/gentoo-static
* leaving sys-devel/gcc in /usr/local/gentoo-static
* leaving sys-kernel/linux-headers in /usr/local/gentoo-static
* leaving sys-libs/glibc in /usr/local/gentoo-static
* leaving sys-devel/gdb in /usr/local/gentoo-static
* leaving metadata/layout.conf alone in /usr/local/gentoo-static
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-binutils.log
* Emerging cross-binutils ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-linux-headers-quick.log
* Emerging cross-linux-headers-quick ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-glibc-headers.log
* Emerging cross-glibc-headers ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-gcc-stage1.log
* Emerging cross-gcc-stage1 ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-linux-headers.log
* Emerging cross-linux-headers ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-glibc.log
* Emerging cross-glibc ... [ ok ]
* Log: /var/log/portage//cross-alpha-unknown-linux-gnu-gcc-stage2.log
* Emerging cross-gcc-stage2 ... [ ok ]
NeddySeagoon_Static ~ # |
That built with gcc x86_64-pc-linux-gnu-7.3.0, binutils x86_64-pc-linux-gnu-2.30 and glibc-2.26-r7 on a Phenom II with the default/linux/amd64/17.0/no-multilib profile.
What crossdev version do you have?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Maquis196
n00b
Joined: 02 Apr 2003
Posts: 62
Location: London
|
| Posted: Mon May 28, 2018 3:57 pm Post subject: |
|
|
Frustrating, I wonder if the "previous" install somehow has broken this.
I had 2017.. something but now using 20180508 and had the same issue. I'm using GCC 6.4.0-r1 with glibc 2.25-r11 (its basically a stage3 install as of friday).
With proof that it works elsewhere - I just uninstalled all the crossdev apps in case somehow the old install was breaking the new one. Sure enough, that seems to have fixed it (how though?; unless the old gcc-stage2, so gcc 4.80 or something, was still lying around from the previous install) and emerge/crossdev used that one? which would make sense considering how it was fixed. Sounds like crossdev needs to check if there's a previous install on an older gcc version to avoid this in the future. Unless I've missed some upgrade notes warning me.
Guess we can mark this as solved for anyone who encounters this in the future, cheers for confirming this does work though, shaved off a lot of research time . |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
