search for: version_str

Set a pointer to syslinux_version()->version_string in mbinfo. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/com32/mboot/mboot.c b/com32/mboot/mboot.c index 8425e06..76ef7a0 100644 --- a/com32/mboot/mboot.c +++ b/com32/mboot/mboot.c @@ -222,6 +222,13 @@ int main(int argc, char *argv[]) /* Add auxilliary informatio...

...o the - * Free Software Foundation, Inc., 59 Temple Place - Suite 330, - * Boston, MA 021110-1307, USA. - */ - -#include <linux/module.h> -#include <linux/string.h> -#include <linux/kernel.h> - -#include "ver.h" - -#define OCFS2_BUILD_VERSION "1.5.0" - -#define VERSION_STR "OCFS2 " OCFS2_BUILD_VERSION - -void ocfs2_print_version(void) -{ - printk(KERN_INFO "%s\n", VERSION_STR); -} - -MODULE_DESCRIPTION(VERSION_STR); - -MODULE_VERSION(OCFS2_BUILD_VERSION); diff --git a/fs/ocfs2/ver.h b/fs/ocfs2/ver.h deleted file mode 100644 index d7395cb..0000000...

Let me know the best way to change the source tree to add in a time to be output from 'dovecot --version'. I've tried the following with no success: mkdir -p /build/work/dovecot-1.1alpha2 cd /build/work/dovecot-1.1alpha2 export LDFLAGS='-L/common/pkgs/sqlite-3.4.1.1/lib64 -R/common/pkgs/sqlite-3.4.1.1/lib64' export PACKAGE_STRING='dovecot 1.1alpha2-2007-08-07' export

...ef7d92d..23429bd 100644 --- a/core/isolinux.asm +++ b/core/isolinux.asm @@ -1034,7 +1034,7 @@ writestr_early equ writestr ; Data that needs to be in the first sector ; ----------------------------------------------------------------------------- -syslinux_banner db CR, LF, 'ISOLINUX ', VERSION_STR, ' ', DATE_STR, ' ', 0 +syslinux_banner db CR, LF, MY_NAME, ' ', VERSION_STR, ' ', DATE_STR, ' ', 0 copyright_str db ' Copyright (C) 1994-' asciidec YEAR db ' H. Peter Anvin et al', CR, LF, 0 diff --git a/core/pxelinux.asm b/core/pxel...

...on.c =================================================================== --- version.c (revision 53385) +++ version.c (working copy) @@ -33,4 +33,4 @@ /* The complete version string, assembled from several pieces. BASEVER, DATESTAMP, and DEVPHASE are defined by the Makefile. */ -const char version_string[] = BASEVER DATESTAMP DEVPHASE VERSUFFIX; +const char version_string[] = BASEVER DATESTAMP DEVPHASE VERSUFFIX SVNVER;

...n use. These functions were added in 0.9.3, and deprecated in favour of names with "xapian_" removed in 0.9.6, so this code will work for any Xapian version from 0.9.3 onwards: #if XAPIAN_MAJOR_VERSION == 0 && XAPIAN_MINOR_VERSION == 9 && XAPIAN_REVISION < 6 string version_string = Xapian::xapian_version_string(); #else string version_string = Xapian::version_string(); #endif So I don't think there's a reason to keep these around longer than we would otherwise. I think removing these in 1.1.0 would be fine, and we should suggest otherwise in the documentati...

Hi, I didn't notice php7 bindings were included since 1.4.2. That's good. But I have some problems with these, I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck with it: php -r 'require "/usr/share/php/xapian.php";var_export(Xapian::version_string());' '1.4.3'Segmentation fault (core dumped) Regards, Pascal Bonne journée Pascal Masschelier - 06 84 59 38 02 / 01 39 15 90 48 - skype: pascal.masschelier On Sat, Apr 1, 2017 at 12:50 AM, Olly Betts <olly at survex.com> wrote: > On Fri, Mar 31, 2017 at 01:59:55PM +0200...

...ll break if xen_domain_handle_t is + not uint8_t[16]. ** */ + uint16_t xen_major_version, xen_minor_version; + uint32_t xen_version; + char xen_extra_version[XEN_EXTRAVERSION_LEN]; + /* guess conservatively on buffer length for Xen version string */ + char xen_version_str[80]; + /* temporary variables used to build up Xen version string */ + char *p = NULL; /* points to next point of insertion */ + unsigned len = 0; /* length of string already composed */ + char *tmp = NULL; /* holds result of itoa() */ + unsigned tmp_len; /* length of next string to...

Hi Another little patch, adding MiniFrame (a frame with small title bar and buttons which doesn''t appear in the desktop taskbar). Also a sample - not very interesting, happy to roll this into something else if that''s better. cheers alex _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

>>>> Where you set the revision number? >>> >>> I do not want to set the revision number in a source file every >>> time I >>> do 'svn update' :) >>> >> >> Ok, so I'm confused. Don't you want the svn revision number to be >> shown when you do llvm-gcc --version? So why wouldn't you want to >>

Hi, I'm using xapian with c# and mono and i'm having a segfault in get_weight. When i print the index variable, the value is clearly too high. I think something write over it. Do you have any idea on how i could trace the beginning of the segmentation fault ? Thanks, -- Yann

On Jul 9, 2008, at 8:47 PM, Tanya Lattner wrote: > > On Jul 9, 2008, at 6:13 PM, Devang Patel wrote: > >> >> On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: >> >>> >>> Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) >>> (LLVM >>> rXXXX)" >>> >>> Where you set the revision number?

Hi all, I mentioned this on the forum but wasn''t sure if anyone was paying attention. I was just wondering if it would be possible to replace the get_something/set_something style methods with the more Rubyish something/something= style (i.e. uniform access). For example, the Button class currently has button.get_label and button.set_label("foo"). It would give me warm,

...ument 2 of type 'Xapian::MatchSpy *' Am I missing something obvious here, or is swig misbehaving? The above works if ms is an instance of xapian.ValueCountMatchSpy, but I need to implement something different to this. I'm running the latest Xapian from Debian sid: >>> xapian.version_string() '1.2.3' Thanks, Munchkin

...' and there are documents that matches this query, it works ok. attached there is a python program that shows the problem. I tried this program with python 2.5 and python 2.6, the xapian version I'm using is the one used together with xappy (a modified version of 1.2.0, according to xapian.version_string()). I tried running this same program in the xapian that comes with Ubuntu (1.0.20) and it doesn't work since chert is not available. can someone help me with this? -- Bruno -------------- next part -------------- A non-text attachment was scrubbed... Name: phrasesearch.py Type: text/x-py...

...31 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM initrd /initramfs-2.6.32-kdev-v1.img what i do is just copy the original section which beginning with title, and then modified it with different version_string. But at last, after selecting the kdev-v1 item from grub's menu, i got a black screen with a cursor blinking in the top-left, and paused there. If i select the original kernel, namely 2.6.32-220.el6.x86_64, all thing is correct. Is the GRUB gets wrong?? My machine is : m...

Hi, I just pushed on github my code for php7 bindings for xapian 1.4 They are based on the excellent PHP-CPP project. Bindings are not complete for now but may be good enough if you doesn't need special weighting nor geo features. You can find them here. https://github.com/pa-m/php7-xapian feel free to use it and propose merge-requests. I have recent node-js binding in my kitchen too,

...I should have made more of a fanfare about them getting added. > But I have some problems with these, > > I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck > with it: > > php -r 'require > "/usr/share/php/xapian.php";var_export(Xapian::version_string());' > '1.4.3'Segmentation fault (core dumped) That's sounds like a known issue with module unload which is already fixed in git and will be solved by the upcoming 1.4.4 release. It's easy to patch the generated code as a workaround - only one line needs changing - see:...

...about them getting added. > > > But I have some problems with these, > > > > I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck > > with it: > > > > php -r 'require > > "/usr/share/php/xapian.php";var_export(Xapian::version_string());' > > '1.4.3'Segmentation fault (core dumped) > > That's sounds like a known issue with module unload which is already fixed > in git and will be solved by the upcoming 1.4.4 release. It's easy to > patch > the generated code as a workaround - only on...

...(C) 2019 Intel Corporation. > + */ > + > +#include <linux/interrupt.h> > +#include <linux/module.h> > +#include <linux/mdev.h> > +#include <linux/pci.h> > +#include <linux/sysfs.h> > + > +#include "ifcvf_base.h" > + > +#define VERSION_STRING "0.1" > +#define DRIVER_AUTHOR "Intel Corporation" > +#define IFCVF_DRIVER_NAME "ifcvf" > + > +static irqreturn_t ifcvf_intr_handler(int irq, void *arg) > +{ > + struct vring_info *vring = arg; > + > + if (vring->cb.callback) > + retur...