Question

0

./configure: error: working directory cannot be determined

rated 0 times [ 0] [ 0] / answers: 1 / hits: 1673 / 2 Years ago, mon, april 11, 2022, 11:00:22

I am extremely frustrated with this error. now it is worth noting that running cd "$(pwd)" and echoing all environment variables, everything seems in order.

I am currently trying to install unrealircd 5.2.0.1 (BUT I get this error when running ANYTHING involving ./configure script)

Here is my output for pretense on my error:

 _   _                      _ ___________  _____     _

| | | |                    | |_   _| ___ /  __    | |

| | | |_ __  _ __ ___  __ _| | | | | |_/ /| /  / __| |

| | | | '_ | '__/ _ /  _ | | | | |    / | |    /  _ |

| |_| | | | | | |  __/ (_| | |_| |_| |  | __/ (_| |

 ___/|_| |_|_|  ___|__,_|_|___/_| _| ____/__,_|



                               Configuration Program

                                for UnrealIRCd 5.2.0.1

[SNIP]

Would you like to pass any custom parameters to configure?

Most people don't need this and can just press ENTER.

Otherwise, see `./configure --help' and write them here:

[] ->

Running with 4 concurrent build processes by default (make -j4).

./configure --with-showlistmodes --enable-ssl --with-maxconnections=9999999 --with-bindir=/root/unrealircd/bin --with-datadir=/root/unrealircd/data --with-pidfile=/root/unrealircd/data/unrealircd.pid --with-confdir=/root/unrealircd/conf --with-modulesdir=/root/unrealircd/modules --with-logdir=/root/unrealircd/logs --with-cachedir=/root/unrealircd/cache --with-docdir=/root/unrealircd/doc --with-tmpdir=/root/unrealircd/tmp --with-privatelibdir=/root/unrealircd/lib --with-scriptdir=/root/unrealircd --with-nick-history=100 --with-permissions=0600 --enable-dynamic-linking

configure: error: working directory cannot be determined

now like i said, I get this error when installing ANYTHING involving a ./configure script.
it is also worth noting that as any user I am unable to run ./configure, with same said errors.

cating /etc/passwd says proper home directory for said users.

Now what is my problem here?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

chilgirlguid

Add To Favorites

Follow

Total Points: 123

Total Questions: 114

Total Answers: 121

Location: Macau

Member since Mon, Nov 16, 2020

4 Years ago

chilgirlguid questions

1 UNCLAIMED network (network/ethernet controller). How to claim?

Mon, Apr 3, 23, 21:29, 1 Year ago

1 Ubuntu 22 VGA Monitor won't Display Login Screen, but Works Afterwards

Sat, May 7, 22, 01:48, 2 Years ago

1 Is wise and safe use "swap file" for PC/Laptops of 8GB or less? either HDD or SSD

Tue, Feb 22, 22, 09:26, 2 Years ago

1 gnome extension to search for active window

Mon, Oct 4, 21, 08:30, 3 Years ago

1 Accessing shared folder on Virtualbox 6.1 - Windows 10 host - Ubuntu 20.04 SERVER guest

Thu, Feb 3, 22, 14:35, 2 Years ago

View All

answered 2 Years ago utilitere · Accepted Answer

By convention, configure is a POSIX shell script that is created from a configure.ac or configure.in template file by the GNU autoconf program - either at install time or before distribution by the software's maintainer.

The error message

configure: error: working directory cannot be determined

comes from a standard autoconf macro named _AC_INIT_DIRCHECK and defined in /usr/share/autoconf/autoconf/general.m4:

AC_DEFUN([_AC_INIT_DIRCHECK],

[m4_divert_push([PARSE_ARGS])dnl



ac_pwd=`pwd` && test -n "$ac_pwd" &&

ac_ls_di=`ls -di .` &&

ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||

  AC_MSG_ERROR([working directory cannot be determined])

test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||

  AC_MSG_ERROR([pwd does not report name of working directory])

You may find more detailed information about the cause of the error in the config.log file. Alternatively, you can run the same code in a non-interactive POSIX shell as follows:

/bin/sh -c '

  ac_pwd=`pwd` && test -n "$ac_pwd" && 

  ac_ls_di=`ls -di .` && ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .`

'

echo $?

or broken down into its individual parts like

/bin/sh -c 'ac_pwd=`pwd` && test -n "$ac_pwd"'; echo $?

One possibility for failure is that the working directory does not have the executable bit set:

$ chmod -x .



$ /bin/sh -c '

  ac_pwd=`pwd` && test -n "$ac_pwd" &&

  ac_ls_di=`ls -di .` && ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .`

'

/bin/sh: 1: cd: can't cd to /home/steeldriver/src/unrealircd