error building brial-1.2.5

[Olivier Guillon]

Hello

I had an error while building sage from source. It may just be a timing issue but it seems the upstream repo for brial has changed name to '.../upstream/sage_brial/' while this change was not yet reflected on servers (where the repo is still '.../upstream/brial/'). Sage built after getting brial spkg directly from the repository.

[Michael Orlitzky]

We split the brial package into "brial" (the compiled library) and
"sage_brial" (the python interface to that library) in trac #29369. Both
of them use the same upstream tarball. What error did you run into?

(Ultimately, sage_brial should just be added to the sage library like
all of the other library interfaces, but this was the easiest solution
to implement/review.)

[Olivier Guillon]

Ok, I just had a 404 error during build because there were no '.../upstream/sage_brial/' to download from at that time. Your answer explains why I was able to build eventually after downloading the brial tarball directly from FTP repository. I'll try to make a separate build without doing it so as to verify if I can reproduce this behaviour and give back more useful info. I wasn't aware of the splitting sorry.

--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/fbMHFgYJq8Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/4810eec3-67fd-8edb-45e3-0aa0f1d3c3f5%40orlitzky.com.

[Olivier Guillon]

I ran in the same issue on a separate build, you'll find the log in the attachment.

[Olivier Guillon]

I forgot to mention I am on Archlinux with kernel 5.6.4 on a Dell XPS 9560.

[Dima Pasechnik]

Note that brial and sage_brial are built off the same tarball
dimpase@penguin:~/sage$ cat build/pkgs/brial/package-version.txt
1.2.5
dimpase@penguin:~/sage$ cat build/pkgs/sage_brial/package-version.txt
1.2.5


dimpase@penguin:~/sage$ cat build/pkgs/sage_brial/checksums.ini
tarball=brial-VERSION.tar.bz2
sha1=5795c0d73b63e9daa5318b0f22514b7797c59823
md5=fddbc0cebfbac161de110acf30a6b89d
cksum=2578889224
upstream_url=https://github.com/BRiAl/BRiAl/releases/download/VERSION/brial-VERSION.tar.bz2

dimpase@penguin:~/sage$ cat build/pkgs/brial/checksums.ini
tarball=brial-VERSION.tar.bz2
sha1=5795c0d73b63e9daa5318b0f22514b7797c59823
md5=fddbc0cebfbac161de110acf30a6b89d
cksum=2578889224
upstream_url=https://github.com/BRiAl/BRiAl/releases/download/VERSION/brial-VERSION.tar.bz2

Thus, if you have upstream/brial-1.2.5.tar.bz present and matching md5
etc checksums,
you should be all set.

But if you have brial from the system, you're in trouble as brial is
not built, so upstream/brial-1.2.5.tar.bz
does not get downloaded, sage_brial can't be built, as here is no
tarball on the mirrors at the URL is tries to use.

For some reason, upstream_url= is not helping here, and mirrors shoud
be fixed to have the tarball at the URL in question too.

As a workaround:

in upstream/, do

wget https://github.com/BRiAl/BRiAl/releases/download/1.2.5/brial-1.2.5.tar.bz2

and re-run the build.

HTH
Dima


PS. Volker - is it easy to create these URLs for sage_brial/ to point
to brial/ on the mirrors?

On Tue, Apr 14, 2020 at 6:07 PM Olivier Guillon
<olivier...@gmail.com> wrote:
>
> I ran in the same issue on a separate build, you'll find the log in the attachment.
>

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/38f740f5-8596-4a74-b718-898624c55947%40googlegroups.com.

[Olivier Guillon]

Ok thanks a lot for the help, everything seems to work for my main source install as I already said. What I did to solve my issue was essentially the same as the workaround you just mentioned. There were some interferences with my system version of brial (brial-1.2.8) it appears.

And, again, congratulations for the great job you're all doing !!!

Olivier.

[Dima Pasechnik]

On Tue, Apr 14, 2020 at 8:55 PM Olivier Guillon
<olivier...@gmail.com> wrote:
>
> Ok thanks a lot for the help, everything seems to work for my main source install as I already said. What I did to solve my issue was essentially the same as the workaround you just mentioned. There were some interferences with my system version of brial (brial-1.2.8) it appears.

I far as I understand, your setup is using brial the C++ library from
your system, (and sage_brial, aka Sage interface to brial the C++
library, is built), so that's not "interference",
it's by design.

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAJJbjsDnL9pFHcSjM6d60WEv0EVwYra%3DMYcriyyBkewK1A230Q%40mail.gmail.com.

[Olivier Guillon]

To be more specific, I'm using two different versions of sage on my computer, the one brought by arch repos (system-wide, labeled as sagemath-9.0-15) and another one build from source from the develop branch of sage on github (local, currently SageMath version 9.1 rc0).

I will verify configure options for the latter when I have some time.

[Olivier Guillon]

Hello,

everything works fine (and with minimal manual intervention) after a little cleanup in my clone of the develop branch : I did make distclean followed by ./bootstrap and  ./configure  before re-building with  make build. 

Thanks a lot for your time and helpful advice !

Olivier