ld not sucking in /usr/lib/crt1.o - or is it me?
Howdy, I installed 5.1 on my laptop, then synced up to -current as of 8 hours ago. I'm trying to build the 1.5 branch of Firebird (the DBMS), but run into the following error: ld ../temp/static.gpre/gpre/cmd.o ../temp/static.gpre/gpre/cme.o ../temp/static.gpre/gpre/cmp.o ../temp/static.gpre/gpre/c_cxx.o ../temp/static.gpre/gpre/exp.o ../temp/static.gpre/gpre/gpre.o ../temp/static.gpre/gpre/hsh.o ../temp/static.gpre/gpre/int.o ../temp/static.gpre/gpre/int_cxx.o ../temp/static.gpre/gpre/jrdmet.o ../temp/static.gpre/gpre/movg.o ../temp/static.gpre/gpre/msc.o ../temp/static.gpre/gpre/par.o ../temp/static.gpre/gpre/pat.o ../temp/static.gpre/gpre/sqe.o ../temp/static.gpre/gpre/sql.o ../temp/static.gpre/gpre/noform.o ../temp/static.gpre/gpre/gpre_meta.o -o ../gen/firebird/bin/gpre_static -L../gen/firebird/lib -lfbstatic -lfbcom mon -lstdc++ -lcurses -lcrypt -lm -lc -leditline ld: warning: cannot find entry symbol _start; defaulting to 0804dc70 /usr/lib/libc.so: undefined reference to `environ' /usr/lib/libc.so: undefined reference to `__progname' gmake[3]: *** [../gen/firebird/bin/gpre_static] Error 1 gmake[3]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake[2]: *** [gpre_static] Error 2 gmake[2]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake[1]: *** [../gen/firebird/bin/gpre_static] Error 2 gmake[1]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake: *** [firebird] Error 2 *** Error code 2 If I add /usr/lib/crt1.o to the file list it works OK. Any reason why ld isn't pulling this in automatically? Feel free to correct me if I'm missing the obvious and if there's a better way of resolving this. Thanks. Regards, Chris Knight Systems Administrator E-Easy Tel: +61 3 6334 9995 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.e-easy.com.au ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: current iso snapshots
Howdy, My Thinkpads (i1200, TP600) work OK, but you can't use ACPI on them with the default DSDT. Press Space at the boot loader countdown, then issue: set hint.acpi.0.disabled=1 boot Your Thinkpad should then boot OK. AFAIK some newer functionality may be lost without ACPI support. If this works for you, then you want to add the following to /boot/loader.conf: hint.acpi.0.disabled=1 AFAICT getting ACPI working properly on a Thinkpad involves learning AML to modify the default DSDT to work correctly with acpica. I haven't got that far yet though. stinkpad - haven't heard that before. Appropriate term when trying to get 5.x running on them... Regards, Chris Knight Systems Administrator E-Easy Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.e-easy.com.au -Original Message- From: Andrew Thomson Sent: Tuesday, 15 July 2003 10:31 To: [EMAIL PROTECTED] Subject: current iso snapshots is there a definitive zone for snapshots of current?? i stumbled upon this but my local mirror doesn't have any.. lftp ntu.tw.freebsd.org:/FreeBSD/snapshots/i386/ISO-IMAGES 5.1-RELEASE didn't like my stinkpad.. i'm ready to try anything!! ;) cheers, ajt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:32 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: [snip] I haven't had DOS for ages!! I really don't want to go that way. I will have to make DOS bootable CD-ROM, etc.. You've got to have it if only for the hibernation file. (Hibernation is worth it IMHO.) From memory, hibernation on the 600 doesn't have BIOS support. It works under Win9x with an extra program, but doesn't work under Windows 2000. I'm happy to be corrected though. I have a DOS partition on my ThinkPad 600, but never managed to get it working. -- | Matthew N. Dodd Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:09 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. That's useful. I shall try this. BTW, if you're not using CardBus cards, the OLDCARD functionality works fine. ie. comment out the cbb, cardbus and pccard devices in your kernel config and add the card and pcic devices. From my dmesg: cbb0: TI1251 PCI-CardBus Bridge mem 0x50102000-0x50102fff irq 9 at device 2.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1251 PCI-CardBus Bridge mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 The 600 uses a TI1250 instead of a TI1251. -- | Matthew N. Dodd Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:09 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. [snip] Hmm, ps2 doesn't specifically show a cardbus device. It does however have a PCIIRQ, which I set to 11,9,7,5 after disabling the parallel port and the sound. Same error crops up as mentioned above. cbb only gets an irq on my TP600 when acpi is loaded, so I'm going back to using OLDCARD. Interestingly, loader ignores my hint.acpi.0.disable=1 and acpi_load=NO settings in /boot/loader.conf and tries loading it anyway - even when manually setting them. Renaming the acpi module fixed it. Running current as of 20 hours ago. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: fetch: multiple choices
Howdy, The webserver is returning a status code of 300 for the file. The webserver response should be including one or more locations from which the file is available. I'd imagine that libfetch/fetch ignores this and moves on to the next available site. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: On Behalf Of Kris Kennaway Sent: Thursday, 21 November 2002 12:31 To: [EMAIL PROTECTED] Subject: fetch: multiple choices What on earth does this mean? mrtg-2.9.26b.tar.gz doesn't seem to exist in /tmp/distfiles/. Attempting to fetch from http://people.ee.ethz.ch/~oetiker/webtools/mrtg/pub/. fetch: mrtg-2.9.26b.tar.gz: Multiple Choices Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Comments on Release Building for -current
Howdy, As the snapshot manager at snapshots.jp.freebsd.org would be aware, current's release building capability is woeful to say the least. A fair bit of tidying up will need to be done for DP2. I've managed to complete a successful release build of current with a checkout of two days ago. For those interested, here's what I had to do: the mfsroot floppy contents were too large FIX: - edit /usr/src/release/i386/drivers.conf and move the following drivers from floppy 2 to floppy3: aue, cue, em, kue, sk, ti, wb, xe, and the SYSV stuff - edit /usr/src/release/scripts/driver-copy2.awk to not error when it encounters the floppy 3 candidates the kern floppy contents were too large FIX: - edit /usr/src/release/i386/dokern.sh and get sed to remove more drivers from MFSROOT. The drivers are: eisa, ahb, isp, ses the fixit floppy contents were too large FIX: - edit /usr/src/release/i386/fixit_crunch.conf and remove the following programs: mount_msdosfs restore rrestore telnet As you can see, all three 1.44MB floppies run out of space. With the above changes, the build just scrapes by. I'd imagine that the changes I made still wouldn't be enough for a release build to be successful for PC98 or Alpha. I'm happy to help resolve the release building issue if anybody is interested. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Comments on Release Building for -current
Howdy, -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 31 July 2002 23:12 To: Chris Knight Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Comments on Release Building for -current [snip] Oof. It's like our binaries are suddenly very bloated. Did this start very recently (like in the past few days?) Perhaps -mcpu=pentiumpro bloats things and we should use NO_CPU_FLAGS when building crunches, etc. We might also want to use -Os instead of -O when building the kernels and crunches as well. I had been doing semi-regular builds (twice weekly) up until early June. However, kernel stability then became an issue for me. Looking at snapshots.jp.freebsd.org, releases stopped being built on June 21, with the exception of July 7 and 8. I've been given some useful suggestions. I shall now go and do some more builds, then summarise the size changes to the list. It will take a while - my -current build box is a PII-300 laptop. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kern.flp too big
Howdy, Just tried a release build of -current. The R/stage/image.kern directory is 1446KB in size. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Release Building - failing at usr/share/doc/usd/13.viref
Howdy, I'm trying to build a FreeBSD-current snapshot release with a -current install as of 28/05/02 1400 GMT and the CVS tree updated to the same date. I've noticed that when -current is installed into the sandbox, groff isn't installed, nor is it built prior to building the usr/share/doc/usd files. The build then fails in usr/share/doc/usd/13.viref. I'm assuming groff isn't built due to c++ issues with the newer gcc import. Is this correct? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Release Building - failing at usr/share/doc/usd/13.viref
Howdy, Disconnecting usr/share/doc/usd/13.viref and usr/share/doc/papers/sysperf from the build process allowed me to build a -current snapshot. I found the reference in the CVS logs (2002/05/15 09:29:45 PDT) that c++ isn't being built. This explains the lack of groff and tbl. There must be some Makefile magic in bsd.doc.mk that allows all the other usd and papers directories to continue, as specific targets are defined in these two offenders. The sysperf target that fails is paper.tmp (not able to find tbl) and the 13.viref target is index.so (unable to find groff). Anyone know the ETA for c++ to be reconnected to the release build? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: multi default routes in freebsd !?
Howdy, -Original Message- From: Vladimir B. Grebenschikov Sent: Tuesday, 21 May 2002 17:25 To: [EMAIL PROTECTED] Cc: Oleg Chebotarev; [EMAIL PROTECTED] Subject: Re: multi default routes in freebsd !? [snip] Times ago there was hack for multipath routing on: ftp://ftp.flirble.org/pub/unix/hacks/FreeBSD/mpath/ but it seems this page now removed. Remove mpath from the above URL and you will find the patches. -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current in Production
Howdy, I'd just like to thank the FreeBSD team for an outstanding job. I've got a FreeBSD-current system in production running an Intranet that has just exceeded one year's uptime. Admittedly, the snapshot I built was 30/10/2000, but it does go to show that current can indeed be used for production systems. The system only ever had one reboot and that was when the installation was migrated to a new box. For those that are interested, the Intranet uses Apache, PHP, Firebird and OpenLDAP for various Web-based management applications/tasks. Again, thanks to everyone responsible for providing a reliable and dependable distribution, even when it's considered unstable and for development purposes only. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Current in Production
Howdy, I would have lucked out if it wasn't reliable :-) If you do all the right things, such as follow the commit logs and test, test, test, you can get a snapshot of current that will prove reliable for a certain number of tasks. It had three months of testing before going into production, so I didn't get any rude shocks, nor was I risking my job. Everyone was aware of the potential for instability and the fallback was to run the apps on a 4.x release or stable. I needed proof by example that FreeBSD development code was just as capable - if not more - as commercial OS releases. I have that well and truly now :-) I liked riding the edge of insanity years ago. I've fallen over the edge since then :-) Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: Jim Bryant [mailto:[EMAIL PROTECTED]] Sent: Thursday, 11 April 2002 14:35 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Current in Production Do you own a Harley? Do the Mosh Pit? You definitely like riding the edge of insanity... -current is always in a state of flux... I say you lucked out... FreeBSD is killer stuff, but, I personally wouldn't risk a job on the odds of getting a stable -current when I needed one... Chris Knight wrote: [snip] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: nss_ldap
Howdy, The FreeBSD support for nss_ldap is only via the BIND IRS interface. See the README.IRS file supplied with nss_ldap on how to get this working on FreeBSD. To actually utilise the nsswitch features, you'll need to get the -current patches on nectar.com and get them compiling and working on -current. Then use the nss_ldap version on nectar.com along with the patches. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ladislav Kostal Sent: Tuesday, 5 June 2001 20:57 To: [EMAIL PROTECTED] Subject: nss_ldap Hello, I'm trying to get nss_ldap work. But it is looking for some includes, which I haven't (nss_common.h, nss_dbdefs.h). And I can not find any installation howto. There is some mention about FreeBSD in README, but nothing particular to this problem. Patches for nss_ldap on nectar.com are for older release. What do I really need to get it work? I have 5.0-20010531-CURRENT, nss_ldap-153, openldap-2.0.11 (20010524). pam_ldap is working correctly... Please help. Ladislav Kostal To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: kernel core
Howdy, I've found the following sequence to be optimal from going from pre-dirpref -current to post-dirpref -current and 4-stable to -current: make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE make installworld mergemaster reboot to single user fsck all partitions, answering yes to all prompts tunefs -A -s n all partitions, where N 0 I found that the newer fsck didn't help any. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Baldwin Sent: Sunday, 22 April 2001 3:27 To: David W. Chapman Jr.; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: kernel core On 21-Apr-01 David W. Chapman Jr. wrote: I just tried to do an installkernel on a new kernel I built and I got the same error except the last line changed to stopped atffs_dirpref+0x210movzbl0(%ECX,%EAX,1),%EAX Do I have any hope at recovering from this or should I start again with 4 and upgrade to -current. I'm assuming is a problem with the kernel and without being able to update the kernel and install a new one, I don't think I can fix it. You need to rebuild fsck and install it and fsck your filesystems. This is the dirpref changes biting you. Warner, we probably need an entry in UPDATING for the dirpref changes that warn people to build and install a new fsck before booting a dirpref kernel. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: md, current and stable
Howdy, -Original Message- From: Sheldon Hearn [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 6 February 2001 20:38 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: md, current and stable On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote: Since the new md was introduced, it is not possible to build a -current snapshot on a -stable box. Are there any plans to MFC this soon? Woah, what's the problem? This sounds like something that should be fixed, not covered up with an MFC. When -current's release scripts were cut over to use mdconfig due to PHK's death warrant notice of vn, vnconfig and MFS, release builds stopped working on -stable due to -stable's md driver not having a handler for /dev/mdctl. As vn + friends are disappearing, it makes sense for md to be MFCed, thus fixing the problem. Ciao, Sheldon. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
md, current and stable
Howdy, Since the new md was introduced, it is not possible to build a -current snapshot on a -stable box. Are there any plans to MFC this soon? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sysinstall move and make release on FreeBSD-stable
Howdy,
Since the sysinstall move, make release on FreeBSD-stable (as of 3 hrs ago)
breaks when building sysinstall. The output is:
=== usr.sbin/sysinstall
cc -o rtermcap /usr/src/usr.sbin/sysinstall/rtermcap.c -ltermcap
rm -f makedevs.tmp
echo '#include sys/types.h' makedevs.tmp
./rtermcap ansi | file2c 'const char termcap_ansi[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25w | file2c 'const char termcap_cons25w[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25 | file2c 'const char termcap_cons25[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25-m | file2c 'const char termcap_cons25_m[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25r | file2c 'const char termcap_cons25r[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25r-m | file2c 'const char termcap_cons25r_m[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25l1 | file2c 'const char termcap_cons25l1[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap cons25l1-m | file2c 'const char termcap_cons25l1_m[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap vt100 | file2c 'const char termcap_vt100[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
./rtermcap xterm | file2c 'const char termcap_xterm[] = {' ',0};'
makedevs.tmp
/usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
then:
cc -O -pipe -Wall -I/usr/src/usr.sbin/sysinstall/../../gnu/lib/libdialog -I.
-I/usr/obj/usr/src/i386/usr/include -c makedevs.c
makedevs.c:4: syntax error before `,'
makedevs.c:7: syntax error before `,'
makedevs.c:10: syntax error before `,'
makedevs.c:13: syntax error before `,'
makedevs.c:16: syntax error before `,'
makedevs.c:19: syntax error before `,'
makedevs.c:22: syntax error before `,'
makedevs.c:25: syntax error before `,'
makedevs.c:28: syntax error before `,'
makedevs.c:31: syntax error before `,'
I did a local hack to copy libc.so.5 into ${CHROOTDIR}/usr/lib before the
chroot command, but this doesn't solve the problem properly. At the moment,
it seems that current snapshots can only be built with current, and I'm not
sure of the correct way to fix this for stable. I'm thinking the best way is
to change the linking command for rtermcap in
/usr/src/usr.sbin/sysinstall/Makefile relative to one of the environment
variables set for the make release process. Not foolproof, but better than
my hack :-)
Also, the following commands added to ${CHROOTDIR}/mk are now dependent on
where sysinstall in the release you're trying to build lives.
cd /usr/src/release/sysinstall
make obj
They've been removed from /usr/src/release/Makefile v1.589, but aren't they
still required if you're trying to build a 4.x release? Or am I missing the
point?
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: modified ich sound driver for current?
Howdy, I modified the mentioned driver when newpcm got kobjified and submitted the patches back to the author. I didn't get a reply. I haven't synced up my laptop to current since about the new year, so I don't know if it works with any changes made. Rather than send the patch to the list, I'll e-mail it to anyone that asks. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tomi Vainio - Sun Finland - Sent: Wednesday, 17 January 2001 8:56 To: [EMAIL PROTECTED] Subject: modified ich sound driver for current? Mixer stuff was modified couple days ago. Does anyone have working ich driver? I got original driver from http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this site is dead. Does author (Katsurajima Naoto) of this driver read FreeBSD mailing lists? Could someone include this driver to current so it get updated? -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Build failure in -current
Howdy, I've been noticing this on my daily builds for the last five days. I've just tried the attached patch, which works for me. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jordan Hubbard Sent: Monday, 18 December 2000 7:00 To: [EMAIL PROTECTED] Subject: Build failure in -current sh ../../conf/newvers.sh BOOTMFS cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking BOOTMFS ffs_inode.o: In function `ffs_truncate': ffs_inode.o(.text+0x2e5): undefined reference to `softdep_slowdown' ufs_lookup.o: In function `ufs_dirremove': ufs_lookup.o(.text+0x1175): undefined reference to `softdep_slowdown' *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message dokern.sh.diff
RE: Build failure in -current
Howdy, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jordan Hubbard Sent: Monday, 18 December 2000 10:54 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Build failure in -current I've been noticing this on my daily builds for the last five days. I've just tried the attached patch, which works for me. Well, that's a fix, just not the right one. :) There should be no "dangling references" to soft updates if SOFTUPDATES is not defined. I realise that. I always use soft updates, so it wasn't a problem for me. It took less time to add it into the boot floppies than work out what a non-softupdates softdep_slowdown should return. - Jordan Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Build failure in -current
Howdy, You beat me to it. I was just about to send a patch that did exactly the same thing. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, 18 December 2000 11:02 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Build failure in -current "Chris Knight" [EMAIL PROTECTED] writes: I've been noticing this on my daily builds for the last five days. I've just tried the attached patch, which works for me. But it does only solve the problem for `make release'. Please upgrade so that you have sys/ufs/ffs/ffs_softdep_stub.c 1.15 which should solve the problem in a more general way. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FFS Snapshot issues
Howdy,
Get the attached panic repeatedly when doing an rm -rf /usr/ports and trying
to create a snapshot of the root partition. Sometimes I get the panic when
there's no apparent disk activity and trying to create a snapshot on 2GB
filesystems. I've included gdb output, dmesg and my kernel config.
Hopefully, some-one can make more sense of it in a shorter timeframe than
me. If any further information is required, please let me know and I'll try
my best to get it to you.
BTW, is there any reason I had to enter panic twice in ddb to get the sucker
to dump core?
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
ait0fd02# gdb -k kernel.0 vmcore.1
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 3362816
initial pcb at 2a7fe0
panicstr: from debugger
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0170fd8
stack pointer = 0x10:0xc3b38f14
frame pointer = 0x10:0xc3b38f24
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 5 (syncer)
panic: from debugger
panic: from debugger
Uptime: 6m21s
dumping to dev #ad/0x20001, offset 344064
dump ata0: resetting devices .. done
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 dumpsys () at ../../kern/kern_shutdown.c:477
477 if (dumping++) {
(kgdb) back
#0 dumpsys () at ../../kern/kern_shutdown.c:477
#1 0xc0175247 in boot (howto=260) at ../../kern/kern_shutdown.c:320
#2 0xc0175685 in panic (fmt=0xc022d5d4 "from debugger")
at ../../kern/kern_shutdown.c:568
#3 0xc011c2b5 in db_panic (addr=-1072230440, have_addr=0, count=-1,
modif=0xc3b38d88 "") at ../../ddb/db_command.c:433
#4 0xc011c255 in db_command (last_cmdp=0xc025be40, cmd_table=0xc025bca0,
aux_cmd_tablep=0xc029f92c) at ../../ddb/db_command.c:333
#5 0xc011c31a in db_command_loop () at ../../ddb/db_command.c:455
#6 0xc011e4c3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#7 0xc02088d2 in kdb_trap (type=12, code=0, regs=0xc3b38ed4)
at ../../i386/i386/db_interface.c:163
#8 0xc0214d54 in trap_fatal (frame=0xc3b38ed4, eva=0)
at ../../i386/i386/trap.c:936
#9 0xc0214add in trap_pfault (frame=0xc3b38ed4, usermode=0, eva=0)
at ../../i386/i386/trap.c:855
#10 0xc0214557 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0,
tf_esi = -1070810528, tf_ebp = -1011642588, tf_isp = -1011642624,
tf_ebx = 0, tf_edx = 1, tf_ecx = -1064877056, tf_eax = 8,
tf_trapno = 12, tf_err = 0, tf_eip = -1072230440, tf_cs = 8,
tf_eflags = 65670, tf_esp = -1070810528, tf_ss = 8})
at ../../i386/i386/trap.c:438
#11 0xc0170fd8 in mtx_exit_hard (m=0xc02cba60, type=0)
at ../../kern/kern_mutex.c:402
---Type return to continue, or q return to quit---
#12 0xc01a9cab in sync_fsync (ap=0xc3b38f7c) at ../../sys/mutex.h:603
#13 0xc01a7c0e in sched_sync () at vnode_if.h:508
(kgdb) quit
ait0fd02# dmesg
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-20001129-SNAP #0: Wed Nov 29 15:12:51 EST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/DEBUG
Timecounter "i8254" frequency 1193168 Hz
Timecounter "TSC" frequency 199430220 Hz
CPU: Pentium/P55C (199.43-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x543 Stepping = 3
Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX
real memory = 33554432 (32768K bytes)
config di pcic0
config di pcm0
config di sn0
config di lnc0
config di le0
config di ie0
config di fe0
config di ed0
config di cs0
config di bt0
config di aic0
config di aha0
config di adv0
config q
avail memory = 29642752 (28948K bytes)
Preloaded elf kernel "kernel" at 0xc0323000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc032309c.
Intel Pentium detected, installing workaround for F00F bug
seq0-15: Midi sequencers.
VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc00c4c13 (c0004c13)
VESA: S3 Incorporated. Trio64V+
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
isab0: Intel 82371SB PCI to ISA bridge at device
Australian Time Servers
Howdy,
According to http://www.eecis.udel.edu/~mills/ntp/clock1.htm,
ntp.syd.dms.csiro.au no longer offers ntp services.
ntp.tip.csiro.au or ntp.ml.csiro.au should be used instead. These are
listed at the above-mentioned location as open access servers.
Here's a diff for sysinstall. Could some-one please commit it. Thanks.
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
--- release/sysinstall/menus.c.orig Wed Mar 15 13:57:59 2000
+++ release/sysinstall/menus.c Wed Mar 15 13:59:27 2000
@@ -1365,9 +1365,9 @@
"ntpdate_enable=NO,ntpdate_flags=none" },
{ "Other", "Select a site not on this list",
dmenuVarsCheck, configNTP, NULL, NULL },
- { "Australia", "ntp.syd.dms.csiro.au (HP 5061 Cesium Beam)",
+ { "Australia", "ntp.tip.csiro.au (HP 5061 Cesium Beam)",
dmenuVarsCheck, dmenuSetVariables, NULL,
- "ntpdate_enable=YES,ntpdate_flags=ntp.syd.dms.csiro.au" },
+ "ntpdate_enable=YES,ntpdate_flags=ntp.tip.csiro.au" },
{ " Canada", "tick.usask.ca (GOES clock)",
dmenuVarsCheck, dmenuSetVariables, NULL,
"ntpdate_enable=YES,ntpdate_flags=tick.usask.ca" },
sendmail 8.10
Howdy, Are there any plans by the FreeBSD team to add sendmail 8.10 to FreeBSD-4.0, or is the sendmail release too late for this to happen? TIA for any info. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: building ports
Howdy, Have a look in bsd.port.mk for the version number that it needs to build with. Then make a copy of /var/db/port.mkversion. Edit /var/db/port.mkversion with the version number that bsd.port.mk requires. I had this same problem when the 34upgrade package had been altered with a new version number, but had not been released as a new package... Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ishmael Sent: Tuesday, 9 March 1999 14:44 To: [EMAIL PROTECTED] Subject: building ports within the last 4 days ive upgraded my system from 3.4-stable to -current. until this morning, i had no problems really, but then (this morning) i no longer was able to build any ports, kept receiving error: Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade kit. Please go to http://www.FreeBSD.org/ports/ or a mirror site and follow the instructions. now there is obviously no upgrade kit for -current and i just did a make world, yet i still get this error. ive also tried deleting my entire ports collection and recvsuping fresh, but still same error. any ideas how to rectify? Jeremy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: how to play with pci128 sound card
Greetings, I also have a Creative Labs Sound Blaster PCI128 installed, and though I followed your instructions below I am not havine what I would call promising results. At 12:21 PM 1/10/99 +0100, Luigi Rizzo wrote: you need a -current system with the pcm device, then I am running 3.1-STABLE, but since your instructions were dated befoe the split, I assumed this would be OK. I have added the pnp0 controller and the pcm0 device to my kernel. /kernel: es1: AudioPCI ES1370 rev 0x00 int a irq 12 on pci0.10.0 /kernel: pcm1: using I/O space register mapping at 0xb800 cd /dev ./MAKEDEV snd1 I have done this. cat somefile /dev/audio When I cat'd a .au file I had on my system there was a pause before I got my prompt back, but complete silence from the speakers. Since I did not get any errors addressing the device, could this be a volume problem? If so, is there any way to adjust the volume. If not a volume problem, do you have any suggestions? Any help appreciated! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Why doesn't Vinum start automatically?
At 04:03 PM 1/30/99 -0800, you wrote: Any ideas why this isn't working? Is it working in -current but not -stable? This led me to believe that he was running -stable and simply posted to the wrong group. I am running -stable. I didn't 'exactly' post to the wrong group. I posted to -stable two days ago, and when I didn't get a repsonese I posted to -current because I know that Greg reads -current. :) Cheers... great project Greg! I second that! Vinum is a very slick module. -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Why doesn't Vinum start automatically?
There have been changes to rc and rc.conf lately to autostart Vinum. But on my system it does not auto load at start and I wind up manually loading the module, reading the config and mounting the volume. Any help if figuring out why this is not working would be appreciated. rc.conf now sets a variable with the drives from to read the config: vinum_slices=/dev/da1 /dev/da2 /dev/da3 /dev/da4 and rc checks for this variable and loads vinum if it is set: if [ -n $vinum_slices ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum read $vinum_slices else echo Can't find /modules/vinum.ko fi fi Any ideas why this isn't working? Is it working in -current but not -stable? -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't mount root. Really need help...
At 06:29 PM 1/25/99 +0100, Leif Neland wrote: On Sun, 24 Jan 1999, Chris Knight wrote: Greetings, I have learned a very valuable lesson. No matter how many time I have made world, I shouldn't do it while I'm tired. Last night I synced my tree and made world. I rebooted, and was going to remake my kernel after the boot. That became an impossibility. Can't you boot kernel.old? Although I have gotten past this, it was not kernel realated. I had made world, but not yet remade my kernel. The problem was in /boot/loader, and I was able to get past it by using /boot/loader.old Thanks for the response though! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Can't mount root. Really need help...
Greetings, I have learned a very valuable lesson. No matter how many time I have made world, I shouldn't do it while I'm tired. Last night I synced my tree and made world. I rebooted, and was going to remake my kernel after the boot. That became an impossibility. After the the message Waiting 15 seconds fopr SCSI devices to settle, and before the listing of my SCSI devices is this ominous message: ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2) At the end of the SCSI device listing, the system starts a reboot. Any help in either understanding what happened or getting the box back online appreciated! Also, if someone could tell me where I could obtain a copy of the boot.flp and fixit.flp for a recent elf build of -current I would really appreciate it. -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Can't mount root. Really need help...
Greetings, I have learned a very valuable lesson. No matter how many time I have made world, I shouldn't do it while I'm tired. Last night I synced my tree and made world. I rebooted, and was going to remake my kernel after the boot. That became an impossibility. After the the message Waiting 15 seconds fopr SCSI devices to settle, and before the listing of my SCSI devices is this ominous message: ffs_mountroot: can't find rootvperror 6: panic: cannot mount root (2) At the end of the SCSI device listing, the system starts a reboot. Any help in either understanding what happened or getting the box back online appreciated! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: New version of Vinum
At 02:13 PM 1/21/99 +1030, you wrote: I've just committed a new version of Vinum with a large number of changes. It works fine here, much better than the old version, but there's just a possibility that things may go wrong. If you have trouble, please let me know immediately. Greg, Was this just committed to -current, or is this also in -stable (now that it exists)? I'd like to move to -stable, but if the latest Vinum mods are going to take a while to move to -current I'll be staying here for the duration. :) -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
