Lol~ Yeah. Well, it is all a learning curve, and I'll take it. I lost patience wiht this before but I'm willing to tr again. I'll work on maybe dong the deb package and see where I go. I'm a bit more comfortable wiht linux, and I will either succeed or fail.
Mine is on a clean system so we'll see if this works. Thanks to all. > On Oct 8, 2016, at 7:12 AM, Steve Matzura <[email protected]> wrote: > > Actually you don't. For instance, you don't want the jack package > because you don't have one. There are others you don't want for the > same reason. I highly recommend you go through PACKAGES.default and > comment out those which you don't want and/or absolutely cannot use. I > did what you are doing the first time I tried building, and I made a > right mess of things. After going through PACKAGES and commenting out > things that are totally inappropriate for operation on a virtual > machine, things went much better. I also had to re-build some of the > sub-packages because they had been updated since 1.1.1 was released, > which is what I was using to build in the first place, and there were > one or two things I had to install that my system didn't have at all. > So the advice I'm giving you isn't just off-the cuff; it comes from > experience trying to do what you are trying to do, and I urge you to > re-think your position and give PACKAGES a look-see at the very least. > > Also, use typescript so you can post us a log of what goes on in the > configure process. That would help somebody a lot smarter than I give > you the best and most useful answers possible. Mine come from my own > experience, which obviously aren't yours, but there is definitely an > intersection of results between the two, and a course of remediation > that has moved me along in the build process--not to complete success, > but a heck of a lot further than I was before I went through PACKAGES > like I am suggesting you try. > > On Fri, 7 Oct 2016 18:58:31 -0700, you wrote: > >> See inline. >>> On Oct 7, 2016, at 5:21 PM, Steve Matzura <[email protected]> wrote: >>> >>> Sarah, >>> >>> Since you're building from source, did you read INSTALL? Did you >>> create a PACKAGES file by copying PACKAGES.default and editing it to >>> remove things you don't need? If the answer to either of these things >>> is no, especially the second item, remediate, then try this: >>> >> I'm on a test machine that's 100 percent clean.. Since i want the full, I >> want *all* of the packages. I did copy the packages.default to packages. >> >>> 1. Never a good idea to build things as a non-privileged (not root) >>> user. su to root and try ./configure again. >> >> The ./config command gives the error to never run as root, so I couldn't. >> Output: >> >> >> ****** Configuring ocaml-cry-0.4.1 >> >> ./configure --with-cry-dir=../ocaml-cry-0.4.1/src >> configure: WARNING: unrecognized options: --with-cry-dir >> configuring ocaml-cry 0.4.1 >> checking for gcc... gcc >> 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 files... o >> checking whether we are using the GNU C compiler... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to accept ISO C89... none needed >> checking build system type... x86_64-unknown-linux-gnu >> checking host system type... x86_64-unknown-linux-gnu >> checking for a BSD-compatible install... /usr/bin/install -c >> checking that calling user is not root... configure: error: configure script >> must not be run with root user! >> >> >>> >>> 2. Before running ./configure, execute the typescript command. This >>> will pipe the output of whatever happens while configure is running >>> into a file called typescript which you can then read and download to >>> post here. After configure finishes, type exit<cr> to stop logging. Of >>> course, if your session is terminated, so is the log, but at least >>> you'll have something to look at after you log in again. >> >> >> The "typescript" command gives me a command not found error message > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Savonet-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/savonet-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
