Guillaume Cottenceau wrote:
>
> Pedro Rosa <[EMAIL PROTECTED]> writes:
>
> > below there is the indication that
> > devel is built by this same pack...
>
> Yes, that's weird; I've forwarded the story to guys that shall answer
> better than me, but I was just thinking of something I think I can submit
> to you: "can we build gcc without requiring gcc?".
>
> :-)
>
Well, once upon a time there was something like this. At first gcc was
built under a weird Only-Great-Guru-Knows-All form and then started
"rebuilding" itself in a few runs. Now gcc seems to build on most
systems by requiring gcc binary from very early stage. Really I don't
know if that old Twilight Zone buildup still exists, but back in 94 I
didn't need for a gcc binary from start.
Anyway the problem here is not that ImageMagick is requiring its own
libraries and includes. The problem is that ImageMagick building process
is pointing to libraries that should already be on /usr/lib,
/usr/X11R6/lib or wherever ld.cache is pointed to. That's a bug and a
serious one. A person cannot build ImageMagick from scratch if he has
not it:
-already installed
-library versions differ from those in the package.
-one as potentially conflicting ImageMagick versions on the machine.
In my case I have a problem that avoids me from installing ImageMagick
binaries in a usual way. I have a KDE2 early beta that works half-well.
Later KDE versions have not be so sane to use. But inside these KDE2
packs there is another version of ImageMagick embedded. Really I don't
want to kill a relatively workable KDE2 for the sake of building some
other progs just because something mistakenly does ld -lMagick into what
is already on the system and not those libraries that have just been
built.
Really I didn't dig too deep, but I have the impression that the problem
comes from a secondary build inside the rpm source tree. The main tree
does build without a hassle if you do it "by hand".
PS: I couldn't resist the temptation to check gcc compilation processes.
I looked through the docs and it seems that the TZ self-genesis buildup
is still there in full force. So... :)
> PS : we shall see, maybe this require is a bug.
>
> --
> Guillaume Cottenceau -- Distribution Developer for MandrakeSoft
> http://www.mandrakesoft.com/~gc/
