-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build bitmanip multilib with linux 64 bit toolchain #1215
Comments
For the Linux toolchain you'll have to edit/override the You may or may not also have issues with canonicalised architecture strings depending on what libraries you are building. This is an ongoing issue with certain aspects of the toolchain, especially with certain multilib configurations. |
Note that |
This is how I would approach building the multilib toolchain that you need:
Note that there is no need to specify the multilib |
Hmmmm... I tried that myself and it failed for some reason - oddly while attempting to build some
Full |
Maybe I'm hitting the same or similar issues here as described in this issue? |
Hi Tommy, thanks for the quick response. |
If you are building a Linux toolchain then why do you think that you need to change the latter? Newlib has nothing to do with the Linux toolchain.
If Unfortunately, there seem to be several fundamental problems with building certain multilib toolchains and I don't understand what they are, never mind how to address them. :-( |
For the Linux toolchain multilibs should be in
But, as I said, if they're there but |
Any update @amitch1999? |
Afraid not, I didn't manage to get those certain multilibs to build, and also not sure how to address that. |
My suggestion here for overriding the default set of multilibs seems to be no longer valid: See here for further background on this: Instead I took this, arguably slightly hacky, approach:
I then edited the
to this alternative set, appending the bitmanip multilibs to the default set:
and then ran the build:
So, using this approach, it is possible to build a multilib toolchain with the required bitmanip multilibs in addition to the default base set of multilibs. I think that there may still be other issues with the way that multilibs are configured/built, but these are separate from the original issue raised here which I consider to be resolved now. |
Actually, this summarises the multilib capabilities of the resulting toolchain more clearly/concisely.
|
Hi, I'm trying to build a linux 64 bit toolchain with the following multilib permutations: rv64imac-lp64, rv64imac_zbs_zbc_zbb_zba-lp64, rv64imafdc-lp64d, rv64imafdc_zbs_zbc_zbb_zba-lp64d.
Build from source hash:
170a9a3045207e3ed4d396f6c4f03e1c7978b0e4
my config line:
../riscv-gnu-toolchain/configure --with-arch=rv64imafdc --with-abi=lp64d --enable-multilib --with-multilib-generator="rv64imac-lp64-- rv64imac_zbs_zbc_zbb_zba-lp64-- rv64imafdc-lp64d-- rv64imafdc_zbs_zbc_zbb_zba-lp64d" --prefix=/scratch/riscv/gnu-workspace/install-collab-linux-64-bitmanip
And
make linux
after.The build finishes fine with no errors, but when I use
-print-multi-lib
on gcc all I get is:.; lib32/ilp32;@march=rv32imac@mabi=ilp32 lib32/ilp32d;@march=rv32imafdc@mabi=ilp32d lib64/lp64;@march=rv64imac@mabi=lp64
Without the bitmanip multilib I requested in the config line, and with 32 bit libraries that were not listed.
This is also the same output I get from
-print-multi-lib
when I config and build with no--with-multilib-generator
at all, and only--enable-multilib
as though it ignores--with-multilib-generator
The text was updated successfully, but these errors were encountered: