Re: Compile problems
Bart Trojanowski <[email protected]>
| Newsgroups | gmane.user-groups.linux.ottawa.general |
|---|---|
| Message-ID | <[email protected]> |
* Andy Civil <[email protected]> [101026 17:51]: > I'm used to doing: > ./configure > make > make install > > but in this case there's no file called ./configure is that normal? tarballs usually come with a README or some other file that tells you how to build things. Not all software uses autotools (and thus not have a configure script). You need to find out what's expected before assuming there is a configure step. What website did you download from? Are there instructions there? > I wanted to see the first error that came out of make, but it scrolls off the > screen. Why does "make | more" not pause it for me? "less" doesn't work either. > Is it something to do with it being stderr? Less will only read from stdin, and not stderr, where make and friends write out errors. You can run something like: make 2>&1 | less The "2>&1" means: "2" take stderr ">&" pipe that to another file descriptor "1" use stdin "| less" will now read from stdin and get the errors from your build. > Any idea why it won't compile? Am I starting on the road to dependency hell? What is your distribution? On Debian you can use 'auto-apt' to automatically install library dependencies for a build. It can be quite useful. auto-apt - package search by file and on-demand package installation tool -Bart -- WebSig: http://www.jukie.net/~bart/sig/ -- OCLUG general discussion list [email protected] http://oclug.on.ca/mailman/listinfo/oclug