Fwd: pkgutils fails to build
Hi, Pkgutils 5.30.0 fails to build on my machine. I seem to be missing some files. Can someone tell me if they should be part of the pkgutils package or that something else should provide them? And in the latter case, what package is responsible for them? I have a fresh Crux 2.3 install so I can't believe it's broken already. Thanks, Diederick. Here's the output: =======> Building '/usr/ports/core/pkgutils/pkgutils#5.30.0-1.pkg.tar.gz'. tar -C /usr/ports/core/pkgutils/work/src --use-compress-program=gzip -xf /usr/ports/core/pkgutils/pkgutils-5.30.0.tar.gz + build + cd pkgutils-5.30.0 + make DESTDIR=/usr/ports/core/pkgutils/work/pkg install g++ -O2 -march=i686 -pipe -DNDEBUG -O2 -Wall -pedantic -D_GNU_SOURCE -DVERSION=\"5.30.0\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MM main.cc pkgutil.cc pkgadd.cc pkgrm.cc pkginfo.cc > .depend g++ -O2 -march=i686 -pipe -DNDEBUG -O2 -Wall -pedantic -D_GNU_SOURCE -DVERSION=\"5.30.0\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c -o main.o main.cc g++ -O2 -march=i686 -pipe -DNDEBUG -O2 -Wall -pedantic -D_GNU_SOURCE -DVERSION=\"5.30.0\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c -o pkgutil.o pkgutil.cc pkgutil.cc:43:21: error: archive.h: No such file or directory pkgutil.cc:44:27: error: archive_entry.h: No such file or directory pkgutil.cc: In member function 'std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, pkgutil::pkginfo_t> pkgutil::pkg_open(const std::string&) const': pkgutil.cc:349: error: 'archive_read_new' was not declared in this scope pkgutil.cc:350: error: 'archive_read_support_compression_all' was not declared in this scope pkgutil.cc:350: error: 'archive_read_support_format_all' was not declared in this scope pkgutil.cc:354: error: 'ARCHIVE_DEFAULT_BYTES_PER_BLOCK' was not declared in this scope pkgutil.cc:354: error: 'archive_read_open_filename' was not declared in this scope pkgutil.cc:354: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:355: error: 'archive_errno' was not declared in this scope pkgutil.cc:357: error: 'archive_read_next_header' was not declared in this scope pkgutil.cc:358: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:361: error: 'archive_entry_pathname' was not declared in this scope pkgutil.cc:363: error: 'archive_entry_mode' was not declared in this scope pkgutil.cc:366: error: 'archive_read_data_skip' was not declared in this scope pkgutil.cc:367: error: 'archive_errno' was not declared in this scope pkgutil.cc:371: error: 'archive_errno' was not declared in this scope pkgutil.cc:377: error: 'archive_read_finish' was not declared in this scope pkgutil.cc: In member function 'void pkgutil::pkg_install(const std::string&, const std::set<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&, const std::set<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) const': pkgutil.cc:388: error: 'archive_read_new' was not declared in this scope pkgutil.cc:389: error: 'archive_read_support_compression_all' was not declared in this scope pkgutil.cc:389: error: 'archive_read_support_format_all' was not declared in this scope pkgutil.cc:393: error: 'ARCHIVE_DEFAULT_BYTES_PER_BLOCK' was not declared in this scope pkgutil.cc:393: error: 'archive_read_open_filename' was not declared in this scope pkgutil.cc:393: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:394: error: 'archive_errno' was not declared in this scope pkgutil.cc:398: error: 'archive_read_next_header' was not declared in this scope pkgutil.cc:399: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:400: error: 'archive_entry_pathname' was not declared in this scope pkgutil.cc:411: error: 'archive_entry_mode' was not declared in this scope pkgutil.cc:414: error: 'archive_read_data_skip' was not declared in this scope pkgutil.cc:424: error: 'archive_entry_set_pathname' was not declared in this scope pkgutil.cc:427: error: 'ARCHIVE_EXTRACT_OWNER' was not declared in this scope pkgutil.cc:427: error: 'ARCHIVE_EXTRACT_PERM' was not declared in this scope pkgutil.cc:427: error: 'ARCHIVE_EXTRACT_UNLINK' was not declared in this scope pkgutil.cc:429: error: 'archive_read_extract' was not declared in this scope pkgutil.cc:432: error: 'archive_error_string' was not declared in this scope pkgutil.cc:440: error: 'archive_entry_mode' was not declared in this scope pkgutil.cc:459: error: 'archive_errno' was not declared in this scope pkgutil.cc:465: error: 'archive_read_finish' was not declared in this scope pkgutil.cc: In member function 'void pkgutil::pkg_footprint(std::string&) const': pkgutil.cc:503: error: 'archive_read_new' was not declared in this scope pkgutil.cc:504: error: 'archive_read_support_compression_all' was not declared in this scope pkgutil.cc:504: error: 'archive_read_support_format_all' was not declared in this scope pkgutil.cc:508: error: 'ARCHIVE_DEFAULT_BYTES_PER_BLOCK' was not declared in this scope pkgutil.cc:508: error: 'archive_read_open_filename' was not declared in this scope pkgutil.cc:508: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:509: error: 'archive_errno' was not declared in this scope pkgutil.cc:511: error: 'archive_read_next_header' was not declared in this scope pkgutil.cc:512: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:514: error: 'archive_entry_mode' was not declared in this scope pkgutil.cc:516: error: 'archive_entry_hardlink' was not declared in this scope pkgutil.cc:517: error: 'archive_entry_pathname' was not declared in this scope pkgutil.cc:522: error: 'archive_read_data_skip' was not declared in this scope pkgutil.cc:523: error: 'archive_errno' was not declared in this scope pkgutil.cc:526: error: 'archive_read_finish' was not declared in this scope pkgutil.cc:535: error: 'ARCHIVE_DEFAULT_BYTES_PER_BLOCK' was not declared in this scope pkgutil.cc:535: error: 'archive_read_open_filename' was not declared in this scope pkgutil.cc:535: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:536: error: 'archive_errno' was not declared in this scope pkgutil.cc:538: error: 'archive_read_next_header' was not declared in this scope pkgutil.cc:539: error: 'ARCHIVE_OK' was not declared in this scope pkgutil.cc:540: error: 'archive_entry_mode' was not declared in this scope pkgutil.cc:548: error: 'archive_entry_hardlink' was not declared in this scope pkgutil.cc:559: error: 'archive_entry_uid' was not declared in this scope pkgutil.cc:569: error: 'archive_entry_gid' was not declared in this scope pkgutil.cc:577: error: 'archive_entry_pathname' was not declared in this scope pkgutil.cc:582: error: 'archive_entry_symlink' was not declared in this scope pkgutil.cc:586: error: 'archive_entry_rdevmajor' was not declared in this scope pkgutil.cc:587: error: 'archive_entry_rdevminor' was not declared in this scope pkgutil.cc:590: error: 'archive_entry_size' was not declared in this scope pkgutil.cc:597: error: 'archive_read_data_skip' was not declared in this scope pkgutil.cc:598: error: 'archive_errno' was not declared in this scope pkgutil.cc:602: error: 'archive_errno' was not declared in this scope make: *** [pkgutil.o] Error 1 -- http://www.diederickdevries.net/
On Sat, May 26, 2007 at 10:05:46PM +0200, Diederick de Vries wrote:
Hi,
Pkgutils 5.30.0 fails to build on my machine. I seem to be missing some files. Can someone tell me if they should be part of the pkgutils package or that something else should provide them?
prt-get depends pkgutils...
Hi, Jesse and Diederick, Jesse Kokkarinen schrieb:
On Sat, May 26, 2007 at 10:05:46PM +0200, Diederick de Vries wrote:
Pkgutils 5.30.0 fails to build on my machine. I seem to be missing some files. Can someone tell me if they should be part of the pkgutils package or that something else should provide them?
prt-get depends pkgutils...
prt-get update doesn't work here, as it doesn't re-evaluate the (sometimes changing) dependencies of a port once it's installed. You need to manually install libarchive. ...and read the announcements on the list. It was mentioned already. Greets, Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19
Hi, On Sun, May 27, 2007 at 20:30:49 +0200, Clemens Koller wrote: [...]
prt-get update doesn't work here, as it doesn't re-evaluate the (sometimes changing) dependencies of a port once it's installed. It does work in the way it's meant to work, due to the dependency model CRUX has applied so far: dependencies are not enforced, and there's no way to tell whether the user ignored a dependency in the past or whether it was added to the port recently. It's a design choice. Using a more strict model for dependencies would make this awkwardness go away, however users' wishes have gone in the opposite direction, which was the reason why the --ignore option was added to explicitely allow users to omit dependencies in dependency calculations.
Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Hi, Johannes! Johannes Winkelmann schrieb:
On Sun, May 27, 2007 at 20:30:49 +0200, Clemens Koller wrote: [...]
prt-get update doesn't work here, as it doesn't re-evaluate the (sometimes changing) dependencies of a port once it's installed.
It does work in the way it's meant to work, due to the dependency model CRUX has applied so far: dependencies are not enforced, and there's no way to tell whether the user ignored a dependency in the past or whether it was added to the port recently.
I am absolutely fine with the current "it does/doesn't work here as it's meant to work". Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). I have some linux folks getting started with this serious distro for educational reasons which could need the one or other hint of what they do or propably didn't... Greets, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19
On Mon, May 28, 2007 at 12:27:16PM +0200, Clemens Koller wrote:
Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). I have some linux folks getting started with this serious distro for educational reasons which could need the one or other hint of what they do or propably didn't...
prt-get has had the same functionality for years and it has worked fine. Dependency tracking is something that is left mostly to the user, and in my opinion, should stay that way. I would also add crux is not the best option for beginners, therefore it would make no sense to begin adding so-called proper dependency tracking and handling. When you use crux, you have to acknowledge that the user has the final say, not the ports system.
Greets, This is not English, stop using it.
On Mon, May 28, 2007 at 02:01:06PM +0300, Jesse Kokkarinen wrote:
Greets, This is not English, stop using it.
"Okay" is not English either, if you are stuck in 1838. Google: Your search - "stop using greets" - did not match any documents. Your search - "greets is not English" - did not match any documents. Results 1 - 10 of about 6,780,000 for "greets". Results 1 - 10 of about 18,400 for "pissing into the wind". Good luck, -- Anton Vorontsov email: cbou@mail.ru backup email: ya-cbou@yandex.ru irc://irc.freenode.org/bd2
On 2007-05-28 at 16:25, Anton Vorontsov wrote:
Results 1 - 10 of about 6,780,000 for "greets". Results 1 - 10 of about 18,400 for "pissing into the wind".
http://en.wiktionary.org/wiki/greets Cheerings, Antti
Hi, Johannes! [...] Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). I don't think this can be added now in a consistent way; especially in
On Mon, May 28, 2007 at 12:27:16 +0200, Clemens Koller wrote: the context of 'install' it's very clear that the user didn't want all dependencies to be pulled in (otherwise he/she would have used depinst). In the past, I've considered adding --install-deps options to install and get rid of depinst (and use the same option for update and sysup), however that would be a major change in the user interface. At the same time, this would allow a configuration option defining the default behaviour of 'install' and 'sysup', i.e. whether they should add new dependencies on their own, allowing to either have a 'convenience system' at the cost of some dependencies being pulled in you would have left out, or a 'full control' system which works just the way it used to work so far. I've always like the idea, however as mentioned that would have meant a major change in the user interface, which is something which I didn't want to do at that point in time.
I have some linux folks getting started with this serious distro for educational reasons which could need the one or other hint of what they do or propably didn't... Since it's impossible for prt-get to tell whether a build error was really due to missing dependencies, a message of warning about omitted dependencies will probably be counter productive for educating folks, since it will a) keep them from thinking on their own, and b) leave them frustrated if the tools suggest a solution and the build keeps failing after following it, with the tool staying silent
Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Hi, Johannes! Johannes Winkelmann schrieb:
On Mon, May 28, 2007 at 12:27:16 +0200, Clemens Koller wrote: [...]
Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). [...] I've always like the idea, however as mentioned that would have meant a major change in the user interface, which is something which I didn't want to do at that point in time.
I wouldn't care about the UI/look and feel/whatever, as long as it's optional. I thought about something like a CRUX_VERBOSE=<value> in the environment for users who want more then no information of what's going on.
Since it's impossible for prt-get to tell whether a build error was really due to missing dependencies, a message of warning about omitted dependencies will probably be counter productive for educating folks, since it will a) keep them from thinking on their own, and b) leave them frustrated if the tools suggest a solution and the build keeps failing after following it, with the tool staying silent
I don't ask for tools to suggest anything which could be misleading. I just don't like tools which stay silent and don't tell what they do or don't do. That's the only thing I would welcome here - in prt-get. Otherwise, I dump most stuff to a file and check what happened, when I am back from coffee. Anyway, what other distro would/could you recommend if he/she(*) asks for a distro which is good to get an idea of how the internals of a Linux system work? I have no glue. (*) sw-developers, programmers, engineers and friends. Have fun, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19
Hi Clemens, On Mon, May 28, 2007 at 18:46:15 +0200, Clemens Koller wrote:
Hi, Johannes!
Johannes Winkelmann schrieb:
On Mon, May 28, 2007 at 12:27:16 +0200, Clemens Koller wrote: [...]
Maybe it's worth a simple message from prt-get install and prt-get update which dependencies are not satisfied (yet). [...] I've always like the idea, however as mentioned that would have meant a major change in the user interface, which is something which I didn't want to do at that point in time.
I wouldn't care about the UI/look and feel/whatever, as long as it's optional. Well, that was kinda my point. The commands didn't have the same meaning as before, so it couldn't be made optional.
Since it's impossible for prt-get to tell whether a build error was really due to missing dependencies, a message of warning about omitted dependencies will probably be counter productive for educating folks, since it will a) keep them from thinking on their own, and b) leave them frustrated if the tools suggest a solution and the build keeps failing after following it, with the tool staying silent
I don't ask for tools to suggest anything which could be misleading. Well, if the build fails, and you print out that the user is missing dependencies, you are in a way suggesting that this may be the problem, and thus the user will expect that getting rid of this warning will make the problem go away. I'd call that misleading.
I just don't like tools which stay silent and don't tell what they do or don't do. That's the only thing I would welcome here - in prt-get. I don't fully understand you here. How does it not tell you what it does?
Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
participants (6)
-
Anton Vorontsov -
Antti Nykänen -
Clemens Koller -
Diederick de Vries -
Jesse Kokkarinen -
Johannes Winkelmann