similar to: syslinux 3.31 will not build on RHEL3

Full_Name: Je Cade Version: R-2.2.1 OS: RedHat 9 Submission from: (NULL) (129.49.108.173) I followed the instructions. tar -xvf, configure, then make. I get these error messages at the end of make and with make check. ================================================================== ================================================================== In file included from rbitmap.c:45:

Hi: I don't know if it is a bug or what? I followed instructions. Jean R version: R-2.2.1 OS: Linux RedHat 9 I followed the instructions. tar -xvf, configure, then make. I get these error messages at the end of make and with make check. ================================================================== ================================================================== In file

Well, it has to happen at some point, so I have officially pushed out SYSLINUX 3.72. The big news in this release is of course the ISOLINUX hybrid mode support (a single image which can be booted either from a CD-ROM or from a hard disk/USB stick), but there are plenty of more goodies in here, including the label listing (not technically completion) on the Tab key. As usual, huge thanks to

Details of installation attached. Effect: when I build and test (with full path names) ssh in the openssh... directory, everything works fine. When I "install" it as per attached file into a test-directory and run it from there, there are 2 phenomena: either it just hangs, eating 96% of CPU or it dies with a Segmentation fault (this is what happens most often) Help needed

On 05/03/2024 01:24, Damien Miller wrote: > > Hi, > > OpenSSH 9.7p1 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This is a bugfix release. > Running the testsuite on Solaris 9 I see this: set -xe ; if /export/home/tgc/buildpkg/openssh/src/openssh-git/ssh -Q key | grep -q ^ssh-rsa ; then \

On Sat, 9 Mar 2024, Tom G. Christensen wrote: [snip] > Running the testsuite on Solaris 9 I see this: [snip] > /export/home/tgc/buildpkg/openssh/src/openssh-git/ssh-keygen -if > /export/home/tgc/buildpkg/openssh/src/openssh-git/regress/rsa_ssh2_crnl.prv | > diff - /export/home/tgc/buildpkg/openss > h/src/openssh-git/regress/rsa_openssh.prv ; \ > fi > +

Hallo, Matt, Du meintest am 25.06.13: [compiling syslinux-6.00] >> Thanks - now it crashes later ... > What crash are you seeing? ------------- cite on ------------- [...] gcc -Wp,-MT,abort.o,-MD,./.abort.o.d -Os -march=x86-64 -falign- functions=0 -falign-jumps=0 -falign-labels=0 -ffast-math -fomit-frame- pointer -std=gnu99 -fno-stack-protector -fwrapv -freg-struct-return -

After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -hpa

When I build syslinux, I normally do make spotless make but this fails with syslinux-3.31 because of 4 files: ./com32/lib/sys/vesa/.background.o.d ./com32/lib/sys/vesa/.drawtxt.o.d ./com32/lib/sys/vesa/.alphatbl.o.d ./com32/lib/sys/vesa/.initvesa.o.d The .initvesa.o.d has some redhat specific path that does not exist on my system: /usr/lib/gcc/x86_64-redhat-linux/4.1.1/include/stdarg.h If

Hi, I'm using Kubuntu and have a problem with the ISOLINUX CDROM booter with versions used since (K)Ubuntu 7.04. The ISOLINUX booter versions 3.36 and 3.53 do not boot my motherboard. The version shipped with Ubuntu 7.04 is I believe ISOLINUX 3.31 but it displays for such a short time I could be wrong. I'm writing to this mail list in case the original Ubuntu bug report never made it

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

Does anybody have any good RHEL3 wireless (802.11) resources? I'm googling and haven't yet found anything good and am hoping someone here can point me in the right direction.

I have several RHEL3 WS machines that were installed here running as servers and their RHN subscriptions were never kept up. Now that I have become responsible for them I would like to move them to CentOS as I can keep them updated as needed. Some of them I can simply migrate to new machines, but a few I can not. Is it possible to simply upgrade a RHEL3 to the latest CentOS 3? If

Hello... A while ago I posted a question about puppet on rhel3. I didn''t like the thought of replacing the default ruby version with a newer one. So I built up ruby 1.8.5 from rhel5 installed into /opt/. The name changed to ruby-opt (ruby-opt-1.8.5, ruby-libs-opt-1.8.5, etc) so that both versions can be installed together. spec file tweeks for ruby, factor, and puppet attached. (If

Thought people might be interested to know that Puppet runs without any problems on RHEL3U8. I''m using Ruby 1.8.6 built from the FC7 rpms. James ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the

Out of curiosity, is anybody using puppet on RHEL3 (or Centos 3) ? If so, how did you get it to work ? Did you build a ruby-1.8.x or does puppet work on the 1.6.x ruby that ships with RHEL3 ? thanks for any pointers, David

Hey folks, I know there''s an old thread about this, and the provided solution to make puppet work on RHEL3 was to recompile a more recent version of ruby. However, I think it would be nice to upgrade ruby from 1.6.8 to 1.8.6 with RPM, so here''s a quick tip for those who have to manage RHEL3 servers and would like to do it with puppet:

Trying to install a digi dgrp driver on RHEL3 runing the XenU kernel. I am looking for a DDK that has the RHEL3 kernel (version 2.4) in it. All the DDK''s available for download use a kernel version 2.6. John Wythe Activant Solutions Inc. 118-1515 Broadway St. Port Coquitlam BC V3C 6M2 Tel: 604-468-1668 Ext 131 Tel: 1-800-663-0718 Fax: 604-468-1667 Email: john.wythe@activant.com

I've been vexed for the last few days about 'net ads keytab' commands not working on my RHEL3 machines, among other problems I've run into trying to use winbind with ADS security mode. I found a bug in RH's Bugzilla describing the problem and managed to decipher a work-around. The resolution is to add to your /etc/krb5.conf the following: [libdefaults] default_keytab_name

The backport of the xenbus code for the 2.4 kernel changed wait_event_interruptible() into wait_event() into a couple of places it looks to deal with the fact that signals weren''t being blocked. This results in an idle domU showing a load-average of 2, which was messing up some work-management tools. The attached patch blocks all signals for the xenbus and xenwatch daemons, instead.