| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Am Mittwoch, 21. April 2004 19:48 schrieb Kevin: |
| 5 |
> On Wednesday 21 April 2004 11:06, Andy Dustman wrote: |
| 6 |
> > On Wed, 2004-04-21 at 09:53, Kevin wrote: |
| 7 |
> > > checking for C compiler default output... configure: error: C |
| 8 |
> > > compiler cannot create executables |
| 9 |
> > > See `config.log' for more details. |
| 10 |
> > |
| 11 |
[...] |
| 12 |
|
| 13 |
Hi, |
| 14 |
|
| 15 |
I had something similar some days before. |
| 16 |
maybe your problem is the same. |
| 17 |
Have a look at /etc/env.d/05gcc and check if the right directories are in |
| 18 |
there. Double-check it and make sure directories are existant and written in |
| 19 |
there. |
| 20 |
Try again now. If you have no success, enter |
| 21 |
# export LD_PRELOAD="/usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.3/libstdc++.so.5 |
| 22 |
# export LD_LIBRARY_PATH="/usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.3/: |
| 23 |
${LD_LIBRARY_PATH}" |
| 24 |
Take care to use paths which are existant on your machine. |
| 25 |
Now you should (re-)emerge gcc and glibc. |
| 26 |
If your system fails building one of those packages play a little bit around |
| 27 |
with "emerge -u" and some package-names (i.e. pam, python and so on). |
| 28 |
Also check /etc/env.d/05gcc as mentioned above again for directories and files |
| 29 |
which could have changed in the meantime. Maybe you have to re-export |
| 30 |
LD_LIBRARY_PATH again if the directory for the gcc-libs changed in the |
| 31 |
meantime. |
| 32 |
It is quite a lot of "try and fail" (known from Windows :-)) but for me it |
| 33 |
worked. |
| 34 |
|
| 35 |
Greetings |
| 36 |
|
| 37 |
Tobias |
| 38 |
-----BEGIN PGP SIGNATURE----- |
| 39 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 40 |
|
| 41 |
iD8DBQFAhreibZe1CSCwYlARArcWAJ4svUhhiwdRSgwezKVhD7V3gjPxBwCdFnag |
| 42 |
9VaaAdcXJkMApKdabjvJoAI= |
| 43 |
=Gl0c |
| 44 |
-----END PGP SIGNATURE----- |
Archives