Re: 64-bit

2007/11/27, Justin Karneges <[email protected]>:
>
> Silly me, I didn't run "./setup".  Now the package gets created.  I still get
> some warnings though.  Are these anything to worry about?

Not fatal, but you should fix it (it's easy), see below.

> -----
> make[2]: Entering directory `/home/jkarneges/work/ap/frontend/gtkfe'
> make[2]: Nothing to be done for `install-exec-am'.
> test -z "/usr/local/share/applications" || /bin/mkdir -p "/tmp/apkg-build-root.2472/usr/local/share/applications"
>  /usr/bin/install -P -m
> 644 'autopackage-launcher-gtk.desktop' '/tmp/apkg-build-root.2472/usr/local/share/applications/autopackage-launcher-gtk.desktop'
> Warning:  ignoring --preserve_context (-P) because the kernel is not
> selinux-enabled.

Again, this is harmless.

> make[2]: Leaving directory `/home/jkarneges/work/ap/frontend/gtkfe'
> make[1]: Leaving directory `/home/jkarneges/work/ap/frontend/gtkfe'
>
> Installing to /tmp/apkg-build-root.2472 ...done
> /home/jkarneges/work/ap/main/makepackage: line 1098: ./configure: No such file
> or directory
> make: *** No rule to make target `clean'.  Stop.
> make: *** No targets specified and no makefile found.  Stop.
> cp: cannot stat `autopackage-manager-gtk': No such file or directory
> WARNING: Manager was not built. Make sure that you remembered to
> run ./autogen.sh in manager/

Have you run autogen.sh in the manager directory?

The result is that you won't get the "Manage 3'rd party programs"
program and your users won't get a nice GUI to uninstall programs
from.

The warnings about GLIBC2.3 symbols can be ignored. The only
difference is people using ancient distros won't be able to run your
packages. This is not an issue on 64bit systems, since they are all
new enough to support it.

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]