| 1 |
On 2/27/10, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> On Saturday 27 February 2010 19:04:09 walt wrote: |
| 3 |
>> On 02/27/2010 10:04 AM, Mick wrote: |
| 4 |
>> > Hi All, |
| 5 |
>> > |
| 6 |
>> > I am trying to install Gentoo on a i7 x86_64 arch machine and libgamin |
| 7 |
>> > fails when I try to emerge syslog-ng (it's a dependency of it). This |
| 8 |
>> > is my first 64bit machine, so I am not sure if I have made more |
| 9 |
>> > mistakes than usual (LOL). This is the error: |
| 10 |
>> > ==================================== |
| 11 |
>> > |
| 12 |
>> > libtool: link: x86_64-pc-linux-gnu-gcc -shared .libs/gamin.o |
| 13 |
>> > -Wl,-rpath |
| 14 |
>> > -Wl,/var/tmp/portage/dev-libs/libgamin-0.1.10-r2/work/gamin-0.1.10/libgam |
| 15 |
>> >in/.libs ../libgamin/.libs/libgamin-1.so /usr/bin /usr/sbin /bin /sbin |
| 16 |
>> |
| 17 |
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 18 |
>> |
| 19 |
>> > -lpthread -march=core2 -msse4 -mcx16 -msahf -Wl,-O1 -Wl,-soname |
| 20 |
>> > -Wl,_gamin.so -o .libs/_gamin.so |
| 21 |
>> > /usr/bin: file not recognized: Is a directory |
| 22 |
>> |
| 23 |
>> Cool, a new libtool trick. It's trying to link an object file with a |
| 24 |
>> directory? Dunno where the real error is, but I'd start with the old |
| 25 |
>> shotgun approach by running lafilefixer --justfixit and see if it helps. |
| 26 |
> |
| 27 |
> That was my first thought too. I ran lafixer and revdep-rebuild after |
| 28 |
> emerging these and the error shown above came up. |
| 29 |
|
| 30 |
grep for pkg-config inside the config.log (and maybe build.log as |
| 31 |
well). I'm betting on pkg-config not being found, although the ebuild |
| 32 |
seems to list it as a dependency. (Maybe your chroot settings affect |
| 33 |
the path?) |
| 34 |
|
| 35 |
IIRC another package did the same for me some months ago (sorry, can't |
| 36 |
remember which). If it couldn't find pkg-config it would still |
| 37 |
complete configure phase without errors -- but cflags and libs |
| 38 |
variables that were supposed to be filled with various `pkg-config |
| 39 |
--libs foo` outputs were in fact filled with the paths from which |
| 40 |
pkg-config was searched for (in vain) during configuration. And IIRC |
| 41 |
the result looked nearly identical to the situation here. |
| 42 |
|
| 43 |
-- |
| 44 |
Arttu V. |
Archives