Re: Hello, a question on Bison build.

[Akim Demaille]

Please, keep this public.

Le 31 déc. 2013 à 11:32, Fang Liu <address@hidden> a écrit :

> Hi,
> 
> I’m not sure if my question meant to be " relocatable on Bison".

What you described here :)

> I will clearify the question here:
> 
> Just take an example, now all happen  on one same host, at my local repo I 
> try compile from source of Bison, build/ install it. Particularly here I 
> don't install to a standard dir like /usr/local etc(I need to ensure it built 
> well before deliver). 
> So before build it i need to pass option to ./configure, like ./configure 
> --prefix=my/customize/dir/  also I need to specify 
> --datarootdir=/some/another/customized/dir/
> After build these lib or bin at my local repo, if goes well I will 
> 'deliver(copy or rsync)' these libs etc of Bison to a central repository for 
> everyone to able to use  it.
> 
> But I notice in the install, it create a folder under the ${datarootdir} 
> /share/, inside evidently it contains some sub-folders which useful later:
> aclocal/  bison/    info/     locale/   man/
> 
> That will be used by binary of Bison at runtime.
> That means at install time(before final deliver), It need already to create 
> that folder /share/  at central repository, which is not so safe.. if i don't 
> specify  this --datarootdir to central one, by default it will create at my 
> local repo one, it means this 'absolute path' will be searched in later 
> runtime of binary (example: runing binary bison --print-datadir  could see 
> one of these path) by no matter which user who use it. Then I need to keep 
> this absolute path at my lcoal, this is also not scientific though...
> 
> Not sure if you understand the constraint here.
> Thanks for help!

As I said, have a look at the script tests/bison, the answer,
BISON_PKGDATADIR, is there.

I don’t understand why you seem to make such a difference
between datarootdir and say bindir, but really, have a look
at the BISON_PKGDATADIR envvar.