#15, gpr2.gpr: Missing units in the relocatable Library_Interface attribute definition#16
#15, gpr2.gpr: Missing units in the relocatable Library_Interface attribute definition#16dsauvage wants to merge 1 commit intoAdaCore:mainfrom
Conversation
…ace attribute definition
|
Hi, I did not manage to reproduce the libadalang build issue. Could you please provide a reproducer? |
|
Apologize i can not send you an automated reproducer
|
|
Thank you for the reproducer! First, I tried building libadalang with alire in relocatable mode, using the same versions, and alr build worked correctly from the libadalang crate. If I understand correctly, you are not using the Could you please elaborate a bit on the commands you ran? I tried using the GPR tools directly as in your comment, but I wasn’t able to reproduce the issue. |
|
Hi, The |
|
Thanks a lot for the reproducer! I gave a look at the installed version of Your PR fixes indeed the error, but not the bug. We will probably merge it because it is an easy workaround, but I would like to understand a bit more the bug before. I will keep you tuned! |
|
I've run into this today. Are those (and maybe some others) private interfaces that should not be listed? |
|
Hi @saper, sorry for the late answer. These private interfaces should indeed not be listed at first. This issue does not occur with the latest version of gprbuild2, so we will see what is possible to do with the alire team. |
|
@Jicquel I believe this has not much to do with alire? I was running this when building the project manually without using Alire much for this. If it is private, it shall not be used by the libadalang. If it needs to be used, it shall be public and published. Or else? |
You're right. As we understand it, the issue here is that even though that unit is not actually used by the project importing the Regarding the Alire topic, this is not directly related to Alire itself, but rather to the version of Many thanks! |
|
@Jicquel shall I install gpr2 using the gprinstall obtained from gpr2? |
|
Yes, it should install gpr2 properly |
|
Sorry, it does not even build with itself an attempt just to install previously built gpr2 with gprinstall 2 fails with this |
|
I don't have the issue locally. I ran the following commands, with a gprbuild already available: What version of gprbuild did you use? |
|
The missing units below have been added to the relocatable Library_Interface attribute definition
GPR2.Build.Jobserver_Protocol.Pipe
GPR_Parser.Private_Converters
GPR2.Build.View_Tables.Update_Sources_List
GPR2.Tree_Internal.Load_Autoconf
Above fix is for instance required to successfully build libadalang (26.0.0), which depends on gpr2 (26.0..0)