On 5/30/19 12:33 AM, Michael Orlitzky wrote:
>
> As yet unexplained is why manually running "bash configure" works, but
> the autoconf bash re-exec does not. My own strace shows that running
> "dash configure" will wind up running
>
> execve("/bin/bash", ["/bin/bash",
On 5/30/19 12:06 AM, John H Palmieri wrote:
>
> I'm guessing that when you run "sh configure", it runs some other "sh"
> from one of those Sage directories, and not /bin/sh.
>
> Running "command -v sh" should tell you which "sh" is running, in case
> that helps.
>
Yeah, nevermind...
On Wednesday, May 29, 2019 at 5:52:26 PM UTC-7, Michael Orlitzky wrote:
>
> On 5/28/19 5:09 PM, Sébastien Labbé wrote:
> >
> > $ cd
> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5/src
> > $ strace sh congiure
> > ...
> > 4000 lines in total including:
> > ...
> >
On 5/28/19 5:09 PM, Sébastien Labbé wrote:
>
> $ cd /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5/src
> $ strace sh congiure
> ...
> 4000 lines in total including:
> ...
> faccessat(AT_FDCWD, "/home/slabbe/GitBox/sage/configure", R_OK) = 0
>
On Wednesday, May 29, 2019 at 10:17:08 AM UTC+2, Dima Pasechnik wrote:
>
> dash is a bit of a problem. I am not sure whether currently it is
> possible to build Sage with sh==dash
>
Well, I have been using this setup for more than 2 years now with no
problem in compiling Sage hundreds of
On Wed, May 29, 2019 at 10:16 AM Dima Pasechnik wrote:
>
> dash is a bit of a problem. I am not sure whether currently it is
> possible to build Sage with sh==dash
hmm, scratch this. it works at least on Debian stable.
> Perhaps modifying pynormaliz to actually use bash for building might
>
dash is a bit of a problem. I am not sure whether currently it is
possible to build Sage with sh==dash
Perhaps modifying pynormaliz to actually use bash for building might
solve this.
On Wed, May 29, 2019 at 9:15 AM Sébastien Labbé wrote:
>
>
>
> On Wednesday, May 29, 2019 at 8:53:37 AM UTC+2,
On Wednesday, May 29, 2019 at 8:53:37 AM UTC+2, Samuel Lelievre wrote:
>
> Tue 2019-05-28 23:09:33 UTC+2, Sébastien Labbé:
>>
>>
>> On Tuesday, May 28, 2019 at 1:40:45 PM UTC+2, Michael Orlitzky wrote:
>>>
>>>
>>> First, can you find out where /bin/sh actually points?
>>
>>
>> Sorry, I do not
Tue 2019-05-28 23:09:33 UTC+2, Sébastien Labbé:
>
>
> On Tuesday, May 28, 2019 at 1:40:45 PM UTC+2, Michael Orlitzky wrote:
>>
>>
>> First, can you find out where /bin/sh actually points?
>
>
> Sorry, I do not know how to answer this question. What command should I
> type?
>
ls -halF /bin/sh
On Tuesday, May 28, 2019 at 1:40:45 PM UTC+2, Michael Orlitzky wrote:
>
> On 5/25/19 12:49 PM, Sébastien Labbé wrote:
> >
> > (sage-sh) $ cd /tmp
> > (sage-sh) $ pwd
> > /tmp
> > (sage-sh) $ sh configure
> > sh: 0: Can't open configure
> >
>
> This means that the "configure" file isn't
On 5/25/19 12:49 PM, Sébastien Labbé wrote:
>
> (sage-sh) $ cd /tmp
> (sage-sh) $ pwd
> /tmp
> (sage-sh) $ sh configure
> sh: 0: Can't open configure
>
This means that the "configure" file isn't coming from your PATH, which
is even more weird (where the hell is it coming from?).
First, can you
sh is not bash. Your man sh seems to show the bash documentation. The
real sh man page is for example available here
https://www.freebsd.org/cgi/man.cgi?query=sh
And there is no such option.
Le 25/05/2019 à 19:22, Sébastien Labbé a écrit :
Maybe it is the case that your sh actually does
> Maybe it is the case that your sh actually does not follow the "shall"
> above.
>
>
It seems so.
When I do
$ sh --version
sh: 0: Illegal option --
which is weird since:
$ man sh
...
--version
Affiche le numéro de version de bash sur la sortie standard
et
Great! I opened
https://github.com/Normaliz/PyNormaliz/issues/56
We should ask Sebastian Gutsche to release a new PyNormaliz
version including the patch.
Vincent
Le 25/05/2019 à 19:15, Sébastien Labbé a écrit :
$ tar xvf PyNormaliz-2.5.tar.gz
$ cd PyNormaliz-2.5/
$ vim setup.py
$ sage -sh
$ tar xvf PyNormaliz-2.5.tar.gz
$ cd PyNormaliz-2.5/
$ vim setup.py
$ sage -sh
(sage-sh) $ pip install .
Processing /home/slabbe/GitBox/sage/upstream/PyNormaliz-2.5
Installing collected packages: PyNormaliz
Running setup.py install for PyNormaliz ... done
Successfully installed PyNormaliz-2.5
All right, we should go with solution 1 then. Could you modify the
setup.py line 63 with
{{{
- subprocess.check_call(["sh", "configure"], env = my_env )
- subprocess.check_call(["sh", "./configure"], env = my_env )
}}}
and try in the build folder (with sage env activated)
$ pip install .
(or
>
> 1) Could you try
>
> $ sh ./configure
>
(sage-sh) $ sh ./configure
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object
Le 25/05/2019 à 18:31, Sébastien Labbé a écrit :
On Saturday, May 25, 2019 at 6:21:49 PM UTC+2, vdelecroix wrote:
On my machine `sh` points to `bash`. Could you try to activate
the Sage shell `sage -sh` go to the pynormaliz temporary build folder
and try
$ sh configure
(instead of $
On Saturday, May 25, 2019 at 6:21:49 PM UTC+2, vdelecroix wrote:
>
> On my machine `sh` points to `bash`. Could you try to activate
> the Sage shell `sage -sh` go to the pynormaliz temporary build folder
> and try
>
> $ sh configure
>
> (instead of $ ./configure that worked)
>
That
On my machine `sh` points to `bash`. Could you try to activate
the Sage shell `sage -sh` go to the pynormaliz temporary build folder
and try
$ sh configure
(instead of $ ./configure that worked)
Le 25/05/2019 à 18:20, Sébastien Labbé a écrit :
On Saturday, May 25, 2019 at 6:18:43 PM UTC+2,
On Saturday, May 25, 2019 at 6:18:43 PM UTC+2, vdelecroix wrote:
>
> $ which sh
>
>
$ which sh
/bin/sh
$ sage -sh
(sage-sh) $ which sh
/bin/sh
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
$ which sh
Le 25/05/2019 à 18:16, Sébastien Labbé a écrit :
$ echo $PATH
$ echo $PATH
/home/slabbe/GitBox/sage:/home/slabbe/GitBox/scripts:/home/slabbe/bin:/home/slabbe/Applications/bin:/home/slabbe/bin:/home/slabbe/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/gurobi800/linux64/bin
$ sh --version
sh: 0:
Didn't you run 'sage -i pynormaliz'?
Le 25/05/2019 à 14:32, Sébastien Labbé a écrit :
This is to say that I was able to reproduce the issue on my laptop this
time (also running Ubunbtu 16.04).
Am I the only one having trouble with :
make pynormaliz
?
--
You received this message
The error message ' configure: error: source directory already configured;
run "make
distclean" there first' seems to indicate that the wrong configure script
is invoked for some reason.
What is the content of $PATH?
What does 'sh --version' show?
On Saturday, May 25, 2019 at 8:32:22 AM
This is to say that I was able to reproduce the issue on my laptop this
time (also running Ubunbtu 16.04).
Am I the only one having trouble with :
make pynormaliz
?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
> configure: error: source directory already configured; run "make
distclean" there first
Is this the make distclean of sage or the make distclean of pynormaliz?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
Is this the make distclean of SAGE or some make distclean for pynormaliz
only?
On Thursday, May 23, 2019 at 11:07:54 PM UTC+2, vdelecroix wrote:
>
> So the PyNormaliz configure script is actually working... you strangely
> obtained an error when it was run via the setup.py script with the
>
So the PyNormaliz configure script is actually working... you strangely
obtained an error when it was run via the setup.py script with the
mysterious
configure: error: source directory already configured; run "make
distclean" there first
Vincent
Le 23/05/2019 à 23:04, Sébastien Labbé a
$ cd /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5/src
$ sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with other copies of Sage on your system.
* Do not use this for installing Sage
This line in your log is also very suspicious
{{{
configure: error: source directory already configured; run "make
distclean" there first
}}}
It comes from the Sage main configure script. It seems that your
install suffers some inconsistencies.
Vincent
Le 23/05/2019 à 22:55, Sébastien
Salut,
Could you try running manually (in the tmp build repo of pynormaliz)
$ sage -sh
$ ./configure
Le 23/05/2019 à 22:55, Sébastien Labbé a écrit :
Bonsoir,
As I reported in sage-release for 8.8.beta6 [1], I get troubles installing
pynormaliz. I pasted the log on framabin here [2]. I am
Bonsoir,
As I reported in sage-release for 8.8.beta6 [1], I get troubles installing
pynormaliz. I pasted the log on framabin here [2]. I am running Ubuntu
16.04.
The discussion started on the closed ticket #27731 [3], but it is better to
continue it on sage-devel.
Sébastien
[1]
33 matches
Mail list logo
