search for: configure'd

...a package that wraps an external c++ library (which I didn't write) that only successfully compiles on 64bit machines. I'd like to make the package broadly available, but is there a way to get it on CRAN if the 32-bit builds break by specifying its 64-bit only somehow? Luckily, I've ./configure'd my R-devel-compiled-from-source to only build x86_64 libs, so I can develop and install my package against that, but trying to `R CMD INSTALL mypackage` using the official R binaries breaks since it also tries to build a 32-bit *.so (I'm on a mac). I see hints in how to limit which archi...

...requiring access to smb servers. It is a shared library built using automake & libtool. It builds samba's smbclient utility linked against the shared library for test. The perpose is to use in gnome virtual filesystem. It is currently used statically linked into midnight commander when configure'd --with-samba. The code is unmodified, only repackaged. This message is posted because it needs LGPL to legally use it. location: wget http://members.home.com/wroberts1/libsamba.tgz There is outated smblib, but my package uses 2.0.5a code, and automake and libtool for portable library bui...

...2:39:38 badcase imap(username): MAIL environment missing and autodetection failed (home /some/home/directory) Now I thought this was covered in a previous fix before (ChangeLog: "2002-12-17 03:00 Timo Sirainen <tss at iki.fi>") but for some reason it's broken again..? The configure args problem has to do with --localstatedir. If i leave it default (PREFIX/var) it forces me (even with non-relative pathnames in the config file) for the socket-files (ssl_parameters_file, login_dir) that should go in /var/run to be put under PREFIX, (/usr/local for NetBSD 1.6). Not too bad,...

On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: >> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: >>> Look at how $LLVM_CONFIGURE is built, the final value is >>> >>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu >>> --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu" >>> >> >> This looks likes its missing some stuff. Make sure the configure line >>...

...0.03.2008, 15:45 -0700 schrieb Tanya Lattner: > On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote: > > > > > Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: > >> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > >>> Look at how $LLVM_CONFIGURE is built, the final value is > >>> > >>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu > >>> --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu" > >>> > >> > >> This looks likes its missing some stuff. Make sur...

Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: > On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > > Look at how $LLVM_CONFIGURE is built, the final value is > > > > --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu > > --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu" > > > > This looks likes its missing some stuff. Make sure the configure line > is exactly as what is...

...tainers suggesting an alternative when I noticed that that R (2.2.1) has it wrong too: edd at basebud:~> R CMD config --cppflags -I/usr/lib/R/include Should I patch this at my end with a softlink /usr/share/R/include -> /usr/lib/R/include or should that be fixed in R? For the record, I configure'd with --datadir=/usr/share/R/share \ --includedir=/usr/share/R/include \ so that I get told about '-I/usr/lib/R/include' is probably a bug. Indeed, src/script/config has an unconditional --cppflags) if test -z "${LIBR}"; then echo "R was not built...

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think this ERROR sholudn't be an error, maybe it should be a warning. My above changes mean libao doesn't need dlopen()...

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think this ERROR sholudn't be an error, maybe it should be a warning. My above changes mean libao doesn't need dlopen()...

On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 12:23 -0400 schrieb Daniel Berlin: >> To clarify, >> >> configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu >> --target=i686-pc-linux-gnu >> >> I do this all the time on my 4 core amd64 box and it works fine. > > There must be some other difference, as I'm doing exactly that: > >>>> export LLVM_GCC_SRC=$HOME/ll...

...asterisk, = zaptel, libpri, speex and any other relevant packages at the same time = as updating other core system libraries. Installing 1.4 is a pain. The individual installers for each relevant = package have to be grabbed from Digium (or a mirror), then saved = somewhere, then untarred, then ./configure'd, then made, then installed. = And in a month's time if something's been updated, the procedure has to = be repeated. It changes updating a server from a 5 minute operation into = an hour or so. Yeah, part of it's laziness, but it's more about efficient use of = employee time....

We have Samba running on many UNIX boxes but this is the first time we have tried to install to a path different from /usr/local/samba Although the configure and Makefile appear correct and place the files into our preferred path (/data2 as opposed to /usr) whenever we run testparm or try to start smbd/nmbd it is looking for smb.conf under /usr/local/samba/lib and a locks directory under /usr/local/samba/var I have obviously missed something very obvio...

In 1.11.1 / git, I have made some changes to the way that you run guestfish, guestmount and the virt tools from the build directory without installing. Firstly you can't just run ./fish/guestfish or ./fuse/guestmount any more and have those programs magically set LIBGUESTFS_PATH. The automagic code was always error-prone and I have removed it. Secondly, all of the run-*-local scripts have

Hi all, I was just trying to build myself a RC3 set of Ogg/Vorbis libs and tools, but the build of libvorbis bombs out on me while making all in examples. I've ./configure'd with no options, which gave no warnings or errors. After that a normal make gives the below attached output. Can anyone tell me what I've done wrong ? I've also tried removing the examples/ directory. After that, I could succesfully install libvorbis, but then vorbis-tools bombs on...

...700 schrieb Tanya Lattner: >> On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote: >> >>> >>> Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner: >>>> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote: >>>>> Look at how $LLVM_CONFIGURE is built, the final value is >>>>> >>>>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu >>>>> --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu" >>>>> >>>> >>>> This looks likes its missing so...

Hi! I'm trying to setup samba 2.2.4 on MandrakeLinux 8.2. The server should act as a file storage for about 25 Windows 2000 clients. Setting up a "basic" server which just serves the files is easy. However, I'd also like to support NT ACLs on the Samba server. Well, what do I have to do, to get it to work? I'm using the Mandrake RPM for 2.2.4, which has ACL support

In order to compile the latest Vorbis library on the Macintosh, the change appended to this message needs to be made to os_types.h.in. Then, anyone who wants to actually build it must first copy os_types.h.in to os_types.h by hand, since MacOS does not include a command line and thus cannot run configure. It really bugs me that the whole "platforms which don't support configure scripts require multiple undocumented stages to build" issue hasn't been addressed yet. It's so simple to address, too -- just as simple as putting instructions for how to do the two-stage build i...