Member Avatar for tagazin

Hello
I would like to install Android SDK but I have problem with ./configure
I looked for my PATH with echo $PATH:
/usr/local/sbin:/usr/local/bin:/usr/sbin
/usr/bin:/sbin:/bin:/usr/games:/bin:/usr/local/bin
/usr/bin/make:/usr/bin/install

What else should I do to install one package?
(I know cd ./name_folder, ls to see my package and after ./configure, make and make install but I cannot run ./configure..
I did sudo apt-get install build-essential and I saw build-essential is already the newest version.
I did sudo aptitude update and sudo aptitude install openssh-client openssh-server but nothing..

can someone help me ?

Thanks in advance

  • 2 Contributors
  • 2 Replies
  • 311 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by tagazin

Dani AI

Generated

Short answer: ’s approach of sourcing the script explains why it ran for — sourcing executes the script inside your current shell, so it will work even if the file isn’t marked executable or lacks a proper interpreter line. That’s a useful quick test, but it’s better to fix the underlying cause so the package builds cleanly.

Practical checklist (do these in order):

  • Confirm a generated configure script actually exists in the source tree. Some projects provide only the autoconf input files and require running the project’s autogen step.
  • If the script exists but won’t execute, give it execute permission and re-run the normal build step. If the script is missing, regenerate it with the autotools helper that the project provides.
  • Check the script’s first line (the shebang) to ensure a valid shell/interpreter is referenced; install the appropriate interpreter if it’s missing.

A few safe commands you can try (run from the source directory):

chmod +x configure
autoreconf -i
./autogen.sh

Note about PATH: the PATH you posted includes entries that look like program files (for example /usr/bin/make) instead of directories. PATH should list directories only; having file paths there points to a bad export in your shell config and can cause confusing behavior. Clean up PATH in your shell startup files so it contains directories such as /usr/bin and /usr/local/bin.

Caution: sourcing a configure script alters your current shell environment, so don’t rely on it as a permanent workaround. If these steps don’t help, post the exact error and a short directory listing showing the configure file’s permissions so next responders can give precise advice.

Recommended Answers

All 2 Replies

Member Avatar for nonshatter

This might be a long shot, but try:

. configure

instead of

./configure

I had a similar hiccup with a recent version of Ubuntu

commented: very kind and helpful +0
Member Avatar for tagazin

Thank you so much! :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.