SOLVED If I try to install build-essential I get a broken packages error

[thriftee]

I'm not exactly sure the reason.  I was able to install gcc ok, but I won't find out what other development related things I will need until I run into them when I try to install something not already packaged up for this distro.

So far, my impressions are quite good of the distro itself.  The things I like most are that its using a very current kernel and xorg, and that it seems to run pretty light out of the box.  I'm hoping to lighten it more for my old clunkers and see if I can get a menu generator working for it.

thanks for any help...

[biffster]

Hi there. I am assuming you are running Microwatt or some other flavor of R8?

If Microwatt, please read the sticky at the top of the R8 forum to see if this addresses your problem, or its something else. If not Microwatt, please tell me exactly the version and 32 or 64bit.

tks
biff

[thriftee]

Sorry, it didnt occur to me that you might have multiple versions of wattOS R8.  This is the one I installed.  Its the 1st one on the download page.

Get wattOS - Microwatt Edition 8 - CDROM - ISO File - BitTorrent

I will go look for sticky

[thriftee]

This is a broken package error I get if I try to install build-essential.  From that respect, I don't think its related to qupzilla. 

I don't really know what causes broken packages.  I just now that if I hit that I should stop and quit without trying to install, because the last time I tried going further and installing anyway (with a different distro), I ended up completely hosed and had to reload from scratch.  IIRC I had used a testing repo while installing some packages, and actually qupzilla was the one, come to think of it, and ended up hosing the OS completely.

So far I've been able to compile and install what I've needed without installing build-essential, but I sippose the problem will surface again...

[thriftee]

I think its gettiing the broken packages error when I try to install g++ (which is also needed for build-essential).

For example, I tried to install enlightenment e19, but can't compile it...

If you need me to run anything to help identify the problem, please let me know .

thanks

PS: I got roxterm running under root now, so am now able to copy/paste the error messages and config.log

If you could take a quick look in case its something simple, please.  I'm not a C programmer, but it appears to me that if the computer is setup properly to compile etc, that this should be able to work...  I just don't know enough to know what's missing...  Google search leads me to think  my repository source list is setup incorrectly, because it looks like I have a newer 2.18 version of libc6 than the standard debian one, so it would make sense to me that anything else I would install would have to be ok with that?

Code: [Select]


root@dv9000a:/home/bobc# cd enlightenment-0.19.0-alpha1
root@dv9000a:/home/bobc/enlightenment-0.19.0-alpha1# ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/bobc/enlightenment-0.19.0-alpha1':
configure: error: C compiler cannot create executables
See `config.log' for more details
root@dv9000a:/home/bobc/enlightenment-0.19.0-alpha1#

Here is the config.log being referred to above.  I have left out the "cache variables" at the end because its so long

Code: [Select]


This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by enlightenment configure 0.19.0-alpha1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = dv9000a
uname -m = i686
uname -r = 3.13-0.bpo.1-486
uname -s = Linux
uname -v = #1 Debian 3.13.10-1~bpo70+1 (2014-04-23)

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:3000: checking build system type
configure:3014: result: i686-pc-linux-gnu
configure:3034: checking host system type
configure:3047: result: i686-pc-linux-gnu
configure:3089: checking for a BSD-compatible install
configure:3157: result: /usr/bin/install -c
configure:3168: checking whether build environment is sane
configure:3223: result: yes
configure:3374: checking for a thread-safe mkdir -p
configure:3413: result: /bin/mkdir -p
configure:3420: checking for gawk
configure:3436: found /usr/bin/gawk
configure:3447: result: gawk
configure:3458: checking whether make sets $(MAKE)
configure:3480: result: yes
configure:3509: checking whether make supports nested variables
configure:3526: result: yes
configure:3621: checking whether make supports nested variables
configure:3638: result: yes
configure:3662: checking for style of include used by make
configure:3690: result: GNU
configure:3761: checking for gcc
configure:3777: found /usr/bin/gcc
configure:3788: result: gcc
configure:4017: checking for C compiler version
configure:4026: gcc --version >&5
gcc (Debian 4.7.2-5) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4037: $? = 0
configure:4026: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.7/lto-wrapper
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
configure:4037: $? = 0
configure:4026: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4037: $? = 4
configure:4026: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:4037: $? = 4
configure:4057: checking whether the C compiler works
configure:4079: gcc    conftest.c  >&5
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: cannot find -lc
/usr/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:4083: $? = 1
configure:4121: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "enlightenment"
| #define PACKAGE_TARNAME "enlightenment"
| #define PACKAGE_VERSION "0.19.0-alpha1"
| #define PACKAGE_STRING "enlightenment 0.19.0-alpha1"
| #define PACKAGE_BUGREPORT "enlightenment-devel@lists.sourceforge.net"
| #define PACKAGE_URL ""
| #define PACKAGE "enlightenment"
| #define VERSION "0.19.0-alpha1"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:4126: error: in `/home/bobc/enlightenment-0.19.0-alpha1':
configure:4128: error: C compiler cannot create executables
See `config.log' for more details


[biffster]

Thriftee if you are new to Linux I would suggest trying the LXDE version of wattOS R8 unless you have a compelling reason to not. (Which I understand of course).

I will be posting a clean wattOS R8.1 in two weeks or so that will likely not being having the issues you are having with dependencies, installing stuff, etc.

tks
biff

[blaze]

I will be posting a clean wattOS R8.1 in two weeks or so that will likely not being having the issues you are having with dependencies, installing stuff, etc.

 

[thriftee]

Thriftee if you are new to Linux I would suggest trying the LXDE version of wattOS R8 unless you have a compelling reason to not. (Which I understand of course).

I will be posting a clean wattOS R8.1 in two weeks or so that will likely not being having the issues you are having with dependencies, installing stuff, etc.

tks
biff

Thanks for the reply Biff.  Yes, I'll mark this solved and give the LXDE version a try, and can wait a couple weeks to try the openbox. again.

Being a "MS Windows Refugee" running mostly on older hardware, I'm looking for an efficient system, both in terms of memory utilization and efficient use of what CPU there is.  Openbox is pretty good there, but not the best, IMO, so its not a bad idea to trry the LXDE

Thanks again for all your efforts

[thriftee]

Followup - I installed the wattOS R8 LXDE (amd64 by mistake), and haven't had any of the broken packages problems

Thanks