GNU bug report logs -
#43532
[feature/native-comp] *.eln file name hashing, algorithm doesn't seem to play nice with NATIVE_FULL_AOT with self-contained builds
Previous Next
Reported by: Jim Myhrberg <contact <at> jimeh.me>
Date: Sun, 20 Sep 2020 13:04:01 UTC
Severity: normal
Done: Andrea Corallo <akrl <at> sdf.org>
Bug is archived. No further changes may be made.
Full log
Message #74 received at 43532 <at> debbugs.gnu.org (full text, mbox):
Aloxaf <aloxafx <at> gmail.com> writes:
> 在 2020/10/1 下午9:19, Andrea Corallo 写道:
>
> Aloxaf <aloxafx <at> gmail.com> writes:
>
> 在 2020/9/30 下午3:13, Andrea Corallo 写道:
>
> Once the package is produced it can be in any directory with no
> restrinction on the name or like in MacOS the pkg directory will be
> called like name.app?
>
> Thanks
>
> Andrea
>
>
> If you mean where it will be installed. It will always be installed to
> / by default, but there is not some special restriction.
> The $pkgdir just like a fake root and install it with AUR should have
> the same directory structure as `make install DSTDIR='/'`
>
> If you mean where the $pkgdir will be. Its value is
> $BUILDDIR/$PACKAGE_NAME/pkg/$PACKAGE_NAME, $BUILDDIR can be configured
> by user.
>
>
> Yes that's what I meant. Okay then if is correct to assume
> $PACKAGE_NAME is know at compile time should be possible on our side to
> offer a build option to specify that while compiling.
>
> You mean something like `./configure --pkgdir=xxx`? That sounds good and flexible.
>
Yes something like, perhaps to begin with something to pass to make as
`make PKGDIR=xxx`.
Andrea
This bug report was last modified 4 years and 278 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.