| View previous topic :: View next topic |
| Author |
Message |
criswell n00b


Joined: 19 Jun 2002 Posts: 2
|
Posted: Sun Jun 23, 2002 6:39 pm Post subject: 'emerge cdtrools' fails because ld cannot find -lscg |
|
|
I have just barely installed and setup a base Gentoo 1.2 on my laptop. This laptop has happily lived with RedHat, Debian, and Peanut Linux (I mention this to show that the problems I'm having aren't hardware compatibility ones). I went to do an emerge of kde and icewm (use kde apps, but live in icewm) but one of the dependant packages is cdrtools.
Halfway through the cdtrools build, it fails and prevents me from continuing to build/install the rest of my system.
From the output of 'emerge cdrtools' itself:
http://www.geekcomix.com/snh/temp/make-errs.txt
It looks like its failing during the build of libscg (which is a scsi library that comes with and is used by cdrtools). Specifically, it claims that a "CONFIG_JIFFIES" is undeclared. Searching through the source code files, I cannot find CONFIG_JIFFIES anywhere.
This is a very irritating problem, and I would imagine that there would be others out there with it... but I cannot find any forum or doc help. Hell, even a search on google turns up little for "CONFIG_JIFFIES".
Anyone else have this problem? Anyone know how to solve it? |
|
| Back to top |
|
 |
tibo n00b


Joined: 05 Jul 2002 Posts: 22
|
Posted: Fri Jul 05, 2002 10:25 pm Post subject: Re: emerge cdtrools' fails because ld cannot find -lscg |
|
|
I had the same problem, tried couple versions of cdrtools and still nothing. Finally I found libscg.a at my Mandrake box and simply copied that one to Gentoo and it just went through.
It's good idea to keep more one then on disto on your disk, because you can always exchange files or compare config files  |
|
| Back to top |
|
 |
rac Bodhisattva


Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Fri Jul 05, 2002 10:41 pm Post subject: |
|
|
Can you try editing /usr/portage/app-cdr/cdrtools/cdrtools-1.11.24.ebuild and changing:
| Code: | src_compile() {
emake || die
} |
to
| Code: | src_compile() {
make || die
} |
I have seen somewhat similar problems with other ebuilds where the parallel make fails to make a needed configuration header before blasting through trying to compile source files that depend on it. _________________ For every higher wall, there is a taller ladder |
|
| Back to top |
|
 |
criswell n00b


Joined: 19 Jun 2002 Posts: 2
|
Posted: Fri Jul 12, 2002 5:17 am Post subject: Actually, fixed another way... |
|
|
I ultimately went through and defined this flag by hand based upon what was in the kernel source (I assume it should be the same). This fixed the problem.
When I upgrade it again, and if I encounter the problem, I'll try this instead. |
|
| Back to top |
|
 |
xkb n00b

Joined: 13 Jun 2002 Posts: 20 Location: Netherlands
|
Posted: Thu Oct 31, 2002 12:55 am Post subject: |
|
|
| Strange thing is I have this error now 2.. I think it is somehow related to upgrading glbic or gcc. |
|
| Back to top |
|
 |
pee n00b

Joined: 19 Nov 2002 Posts: 2
|
Posted: Tue Nov 19, 2002 12:23 am Post subject: |
|
|
your build is probably failing to build libscg earlier to to a problem with scsi.h,
i'm not sure what the real problem is with this header, but it doesn't include
whatever should define u8.
quick hack is to edit linux/include/scsi.h and change the line that says
u8 scsi_lun[8];
to
unsigned char scsi_lun[8];
or
u_char scsi_lun[8];
or whatever makes you happy ;p
-pee |
|
| Back to top |
|
 |
pjp Administrator


Joined: 16 Apr 2002 Posts: 15989 Location: Colorado
|
Posted: Tue Nov 19, 2002 2:20 am Post subject: |
|
|
Moved from Installing Gentoo, as this is a post installation issue. _________________ Safety is my gaol.
US Constitution | Amendments |
|
| Back to top |
|
 |
kavel n00b


Joined: 21 Apr 2002 Posts: 20 Location: Hillsboro, OR
|
Posted: Fri Nov 22, 2002 11:36 pm Post subject: |
|
|
| I was having the exact same problem when I remembered that I downloaded new kernel-sources a couple of days ago and changed the usr/src/linux link accordingly. In other words, /usr/src/linux was not pointing to the source od the running kernel at the time. I fixed it, and everything went perfectly after that. |
|
| Back to top |
|
 |
|