On Wed, May 14, 2008 at 2:14 PM, Dan McGee <[EMAIL PROTECTED]> wrote: > > On Wed, May 14, 2008 at 6:50 AM, Xavier <[EMAIL PROTECTED]> wrote: > > On Wed, May 14, 2008 at 1:16 PM, Allan McRae <[EMAIL PROTECTED]> wrote: > >> Can we add a check on the libarchive version number when configuring > >> pacman. You can run configure without a problem with a libarchive 1.x > >> version but not actually complete the build. See > >> http://bbs.archlinux.org/viewtopic.php?pid=367593 > >> > >> I know next to nothing about libarchive so I am giving this to someone > >> else to take care of! > >> > > > > I doubt many ppl are still trying to build pacman with libarchive 1.x. > > Yeah, one did but well.. > > But in any cases, I am curious to know how to check version number at > > configure time. I don't know how to do it either. > > Though I believe I know one way to prevent the specific error that > > user was having. We could replace this stuff in configure.ac : > > # Check for libarchive > > AC_CHECK_LIB([archive], [archive_read_data], , > > AC_MSG_ERROR([libarchive is needed to compile pacman!])) > > by this : > > # Check for libarchive > > AC_CHECK_LIB([archive], [archive_read_open_filename], , > > AC_MSG_ERROR([libarchive is needed to compile pacman!])) > > > > What I don't know is when this read_open_filename function was introduced. > > And also what is the oldest libarchive version with which pacman is > > guaranteed to work. > > I would suggest someone grab the last libarchive 1.X release and the > first libarchive 2.X release and compare the header files. See if > there is an new function introduced in 2.X that we can use instead to > verfiy you are using a new enough version. >
Actually it's silly, this archive_read_open_filename function appeared between 1.2.38 and 1.2.57, the two only 1.2.x releases left there : http://people.freebsd.org/~kientzle/libarchive/src/ That 1.2.53 version this guy was using on debian doesn't even exist anymore. And that's indeed the version debian stable is using. (testing has 2.4.11 and unstable has 2.4.17). I don't know if pacman would work with 1.2.57 :P _______________________________________________ pacman-dev mailing list [email protected] http://archlinux.org/mailman/listinfo/pacman-dev
