similar to: FLAC 1.0 Debian packages available

On Wed, Jul 25, 2001 at 06:21:14PM -0400, Matt Zimmerman wrote: > I just uploaded flac 1.0-1 to Debian unstable; it should appear in the archives > tomorrow. In order to get things to work correctly with libtool 1.4, I had to > apply the following patch: > > --- flac-1.0.orig/ltmain.sh > +++ flac-1.0/ltmain.sh > @@ -1862,6 +1862,7 @@

I was curious how widespread bad usage of FileCheck prefixes is in the LLVM/Clang test suite. Running the attached script yields over 200 tests (~1.5%) which are essentially broken because they contain checks that are never checked. Most widespread is the usage of the "CHECK" prefix while all FileCheck invocations have an explicit check prefix. Then there are quite a few prefixes that

I'm trying to build an executable for a program I wrote. The compilation steps go well, but the linking step fails with a libtool "version mismatch" error. My linking command has this prefix: /path/to/R/bin/R CMD LINK gcc -g -std=gnu99 ... etc. The error looks like this: libtool: Version mismatch error. This is libtool 2.2, but the libtool: definition of this LT_INIT comes from

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: aquette > Date: Sat Nov 15 22:47:26 2008 > New Revision: 1557 > > Log: > GNU libtool update > > Modified: > trunk/ChangeLog > trunk/configure.in > trunk/ltmain.sh I think 'ltmain.sh' is a generated file (at least, I hope it is), this change severely broke compilation here. I had to

--- Ben Hines <bhines@alumni.ucsd.edu> wrote: > At 10:39 AM -0700 5/21/02, Josh Coalson wrote: > >--- Ben Hines <bhines@alumni.ucsd.edu> wrote: > >> I guess the problem is really why is it trying to relink it? > >> > >> The "parse error: condition expected:" is suspicious, though.. > maybe > >> it's another "zsh as

On Fri, Jul 20, 2001 at 02:42:21PM -0700, Josh Coalson wrote: > --- Matt Zimmerman <mdz@debian.org> wrote: > > It does work, but gives a warning: > > > > *** Warning: Linking the shared library libFLAC.la against the *** static > > library ia32/libFLAC-asm.a is not portable! > > > > I think this is just because libtool can't determine whether the

On Thu, Jul 19, 2001 at 02:56:11PM -0700, collver@linuxfreemail.com wrote: > On Thu, Jul 19, 2001 at 05:01:07PM -0400, Matt Zimmerman wrote: > > Once I removed that, it also seems to hate the .nasm extension: > > > > /bin/sh ../../../libtool --mode=compile \ > > sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm > > libtool: compile:

I haven't been here during the development, and I haven't yet looked at the source, but the end result is so impressive that it's moving me to comment: In this great free software world we live in, it is rare to find a project so well researched, designed, executed, and presented as FLAC. It fits my needs beautifully, aligns with my political interests, and has been rock solid

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sun Nov 16 13:00:30 2008 > New Revision: 1560 > > Log: > Generated by libtool and should not be versioned. > > Modified: > trunk/ (props changed) Right, that didn't work out quite the way I intended. Can someone please set the svn:ignore property on

I'm trying to build upstream source on RHEL 7.5 and get this error: # autoreconf -i libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying

finished hooking up the altivec stuff so it works in ProjectBuilder. I ran a test, doing a 'flac -t' on 400MB of files compresses at level 5. the runtime dropped from from 180 sec to 105 sec! once I get the latest autotools on my ibook I'll try and get asm compilation to work that way. Josh --- Josh Coalson <xflac@yahoo.com> wrote: > OK, checked it all in (only minor

Hi all! Do you have any idea about the following error message from virt-manager. I was trying to start it with "sudo virt-manager". Do you think I can fix this by simply restarting libvirtd? Regards, Allen Error starting Virtual Machine Manager: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS

I've been playing around with virt-manager. Set up a single vm and enabled autostart, then rebooted the host to test it. It does work, but I can no longer use virt-manager. virt-viewer works, though. 22:17:04,529 (cli:71): virt-manager startup 2012-02-02 22:17:04,530 (virt-manager:292): Launched as: /usr/share/virt-manager/virt-manager.py --debug --no-dbus 2012-02-02 22:17:04,530

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

I am working on getting the CentOS 3/Red Hat Enterprise 3 buildbot going, but I have hit a problem with the latest SVN build. Running './configure' works without any errors, (but I do note that it takes a long time on the drivers directory Makefile). Here is a copy of the configuration summary: Configuration summary: enable SSL development code: yes enable IPv6 support: yes build CGI

I've used R for a couple of years on FreeBSD with few problems. Recently, a couple of the contributed packages seem to have difficulty finding symbols in the shared libraries. Currently, I'm running R 1.3.1 on FreeBSD 4.4. I've tried setting LD_LIBRARY_PATH to /usr/local/lib and some other things. The packages I've had trouble with are: Matrix 0.3.15 RODBC 0.8.3 RSPython 0.3

Hello, I can compile metadata plugin using debian squeeze + wheezy. But build on suse enterprise server 9,10 and 11 failed. The metadata plugin require autoconf-2.65 which i too new. On the other side I can build the dovecot-2.2.4 and pigeonhole-0.4.0 plugin without problems: dovecot require autoconf-2.59 and pigeonhole does not require any specific autoconf version. I asked the authors of the

All, I have just finished uploading the source release for FLAC 1.0.4 beta to Sourceforge; there are no binary releases. See the included doc/html/news.html for the changes since 1.0.3; there are quite a few. http://prdownloads.sourceforge.net/flac/flac-1.0.4_beta-src.tar.gz?download Please beat up on this as much as possible in the next week or two and try and turn up bugs. Here's a

I started with: - Mac OS X 10.5.8 - Xcode installed - OCaml from GODI - qemu from git autoconf is really ancient (2.61). It doesn't have AM_SILENT_RULES and although we tried to make things work when autoconf lacks this by having: m4_ifndef([AM_SILENT_RULES], [m4_define([AM_SILENT_RULES],[])]) AM_SILENT_RULES([yes]) # make --enable-silent-rules the default. this nevertheless

when i build dovecot in my computer, something has occured like below: root at 2030c8624e88:/dovecot-2.3.9# ./autogen.sh --2019-12-04 10:49:53-- https://www.dovecot.org/tmp/wiki2-export.tar.gz Resolving www.dovecot.org (www.dovecot.org)... 94.237.12.234, 2a04:3545:1000:720:acc1:5bff:fe5e:4e9 Connecting to www.dovecot.org (www.dovecot.org)|94.237.12.234|:443... connected. HTTP request sent,