On 2019-09-30 19:22 +0200, Thomas Trepl via blfs-dev wrote:
> Hi all,
> 
> so far i have built a nice Xfce system avoiding python2, gtk2 and
> rustc at all and Xfce-4.14 builds/runs fine without gtk2. For librsvg
> i use the old non-rust version 2.40.20 which still works pretty well -
> ok, i know, thats not really the way to go but building gigabytes of
> compiler stuff just for one lib?
> 
> But now, for firefox it seems that there's no way around. All of
> browsers have downsides (epihani needs webkitgtk needs gtk2, falcon
> needs Python2, seamonkey needs gtk2, firefox needs rustc,gtk2). All i
> need is a good browser so unfortunatly i need to "die some kind of
> death".
> 
> Well i started to fool around with rust and tried to package using the
> DESTDIR mechanism.
> 
> In rusts config file the prefix is specified
> 
> [install]
> prefix = "/opt/rustc-1.35.0"
> 
> and according to the instructions we create that dir upfront. Since
> book also uses DESTDIR strategy I thought "ah, its easy, just put my
> DESTDIR there instead of $pwd/install" and left out the creation of
> the /opt/rustc-1.35.0 out because i do not install in "real"
> locations.
> 
> Badly enough, install failed with an error message like "/opt/rustc-
> 1.35.0 cannot be canonicalized" or such.
> 
> After a few re-runs of building rustc (much fun it is to wait and do
> it again because of a typo in the build script...) I ended up with
> creating the $prefix dir on the build machine even DESTDIR install
> puts the files somewhere else.
> Looking at Arch's instructions, they do pretty much same but their
> $prefix is "/usr" which obviously already exists on building machine.
> 
> Have you ever tried to install rust via DESTDIR and if yes, did you
> see same issue and if yes, how did you work around?

Yes.  I had to "mkdir /opt/rustc-{version}".
-- 
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to