[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #60998] fatal: unable to find current director
From: |
BaldStrong |
Subject: |
[Octave-bug-tracker] [bug #60998] fatal: unable to find current directory |
Date: |
Mon, 2 Aug 2021 10:49:20 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36 Edg/91.0.864.59 |
Follow-up Comment #4, bug #60998 (project octave):
[comment #3 comment #3:]
> Afaict, "get_current_dir_name" isn't part of the POSIX specifications [1].
So, we can't use it (at least not unconditionally).
>
> Does it also work if you replace that line with the following (i.e., using
the system's getcwd instead of gnulib's implementation)?
>
> char *tmp = getcwd (nullptr, 0);
>
>
> [1]: https://linux.die.net/man/3/get_current_dir_name
-------------------------------------------------------
As you said:
../liboctave/system/lo-sysdep.cc: In function ‘std::string
octave::sys::getcwd()’:
../liboctave/system/lo-sysdep.cc:76:35: error: too many arguments to function
‘std::string octave::sys::getcwd()’
char *tmp = getcwd(nullptr,0);
^
../liboctave/system/lo-sysdep.cc:53:5: note: declared here
getcwd (void)
^~~~~~
../liboctave/system/lo-sysdep.cc:76:35: error: cannot convert ‘std::string
{aka std::basic_string<char>}’ to ‘char*’ in initialization
char *tmp = getcwd(nullptr,0);
^
CXX liboctave/util/libutil_la-glob-match.lo
make[2]: *** [Makefile:24609: liboctave/system/libsystem_la-lo-sysdep.lo]
Error 1
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60998>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/01
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Rik, 2021/08/01
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Markus Mützel, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory,
BaldStrong <=
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, John W. Eaton, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Markus Mützel, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Markus Mützel, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Markus Mützel, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, BaldStrong, 2021/08/02
- [Octave-bug-tracker] [bug #60998] fatal: unable to find current directory, Markus Mützel, 2021/08/02