Re: PEBKAC
Both standard-supfile and kernel-supfile were edited to use the "." tag along with the CVS server being cvsup.FreeBSDS.org; but, I'm still getting the version error for config(8). It seems to me that my problem may be the base system is out of sync with the source- I'm using Whitehorn's 2010 snapshot because the recent versions won't load on my machine. Not too sure about compiling config from usr.sbin since doing this the recent time caused errors. So, I'm thinking that either I need to keep "make buildkernel" from checking config version- which I don't know how to do- or wgetting version 600010 of config(8)- of which I don't know which server has that version. On 2/26/12, Kevin Oberman wrote: > On Sat, Feb 25, 2012 at 9:09 PM, Super Bisquit > wrote: >> Okay, >> Will I need to restate all as "10_CURRENT" for the >> kernel(standard)-supfile or should I use the cvs-supfile as the >> template with 10.0_CURRENT as the tag? > > You will need to change the tag in the standard supfile to: > *default release=cvs tag=. > > The name 10-Current is used in discussions, but current is not tagged. > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6...@gmail.com > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PEBKAC
On Sat, Feb 25, 2012 at 9:09 PM, Super Bisquit wrote: > Okay, > Will I need to restate all as "10_CURRENT" for the > kernel(standard)-supfile or should I use the cvs-supfile as the > template with 10.0_CURRENT as the tag? You will need to change the tag in the standard supfile to: *default release=cvs tag=. The name 10-Current is used in discussions, but current is not tagged. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PEBKAC
On Sun, Feb 26, 2012 at 12:09:47AM -0500, Super Bisquit wrote: > On 2/25/12, Glen Barber wrote: > > On Sat, Feb 25, 2012 at 11:23:10PM -0500, Super Bisquit wrote: > >> Machine: PowerPC 7445 Kernel 9.0 > >> I've used. Entered "env -i" stated as prefix to "make buildkernel > >> KERNCONF=$VERSION" command. > >> > >> Kernel build stops with following immediate error: > >> "ERROR: version of config(8) does not match kernel! > >> config version = 67, version required = 600010. > >> > >> Okay. Now I've looked at the standard-supfile and notice that the tag > >> is at RELENG=8. > >> > >> Now, if I change this to tag=RELENG_10- and I've already asked for > >> where the 10.0 sources are with no replies- will the system crap out > >> on me? > > > > I don't know about PPC-specific stuff, but the tag should be "tag=." for > > HEAD (aka, 10-CURRENT). > > > > Okay, > Will I need to restate all as "10_CURRENT" for the > kernel(standard)-supfile or should I use the cvs-supfile as the > template with 10.0_CURRENT as the tag? > I'm not entirely sure I understand your question. You should not sepecify 10-anything in supfiles for HEAD - 10-anything doesn't exist. For HEAD, you want to use "." as the tag. Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PEBKAC
Okay, Will I need to restate all as "10_CURRENT" for the kernel(standard)-supfile or should I use the cvs-supfile as the template with 10.0_CURRENT as the tag? On 2/25/12, Glen Barber wrote: > On Sat, Feb 25, 2012 at 11:23:10PM -0500, Super Bisquit wrote: >> Machine: PowerPC 7445 Kernel 9.0 >> I've used. Entered "env -i" stated as prefix to "make buildkernel >> KERNCONF=$VERSION" command. >> >> Kernel build stops with following immediate error: >> "ERROR: version of config(8) does not match kernel! >> config version = 67, version required = 600010. >> >> Okay. Now I've looked at the standard-supfile and notice that the tag >> is at RELENG=8. >> >> Now, if I change this to tag=RELENG_10- and I've already asked for >> where the 10.0 sources are with no replies- will the system crap out >> on me? > > I don't know about PPC-specific stuff, but the tag should be "tag=." for > HEAD (aka, 10-CURRENT). > > Glen > > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PEBKAC
On Sat, Feb 25, 2012 at 11:23:10PM -0500, Super Bisquit wrote: > Machine: PowerPC 7445 Kernel 9.0 > I've used. Entered "env -i" stated as prefix to "make buildkernel > KERNCONF=$VERSION" command. > > Kernel build stops with following immediate error: > "ERROR: version of config(8) does not match kernel! > config version = 67, version required = 600010. > > Okay. Now I've looked at the standard-supfile and notice that the tag > is at RELENG=8. > > Now, if I change this to tag=RELENG_10- and I've already asked for > where the 10.0 sources are with no replies- will the system crap out > on me? I don't know about PPC-specific stuff, but the tag should be "tag=." for HEAD (aka, 10-CURRENT). Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PEBKAC
Machine: PowerPC 7445 Kernel 9.0 I've used. Entered "env -i" stated as prefix to "make buildkernel KERNCONF=$VERSION" command. Kernel build stops with following immediate error: "ERROR: version of config(8) does not match kernel! config version = 67, version required = 600010. Okay. Now I've looked at the standard-supfile and notice that the tag is at RELENG=8. Now, if I change this to tag=RELENG_10- and I've already asked for where the 10.0 sources are with no replies- will the system crap out on me? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: fifo_listen: fchmod public/pickup: Invalid argument with postfix on today's current
On 02/25/2012 06:34, Giovanni Trematerra wrote: > On Sat, Feb 25, 2012 at 8:15 AM, Doug Barton wrote: >> On 02/24/2012 21:00, Doug Barton wrote: >>> I'm on today's -current (r232126) and I'm getting the error in the >>> subject when trying to start postfix. I recompiled 2.9, and then tried >>> 2.8 both give the same error. >> >> Backing out r232055 fixed this. >> > > Hi Doug, > sorry for the breakage. > It should be related to a behavior change in handling fo_chmod/fo_chown for > named pipes due to r232055. > > Could you try the patch at > http://www.trematerra.net/patches/fifo_chmod.patch > > to see if it fixes your issue with postfix? Yes, it did, thanks. To answer the other question, yes, I always do world & kernel, unless 'svn up' only shows changes under sys/. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: rtld or lang/gcc cannot find libgcc_s.so.1
On Sat, 25 Feb 2012 10:41:59 -0800 Tim Kientzle wrote: > > On Feb 23, 2012, at 9:16 AM, Alexander Kabaev wrote: > > > On Tue, 21 Feb 2012 21:11:13 -0800 > > Tim Kientzle wrote: > > > >> > >> If I understand correctly, the libgcc in base is pretty stripped > >> down compared to "regular" libgcc, because most of that > >> stuff is in our libc instead. > >> > > > > You understand it a bit wrong, but your conclusions are correct. > > libgcc in base is not stripped in any way and is supposed to be > > identical to one coming from upstream. > > So where is __umodsi3 supposed to be defined for ARM? > > In FreeBSD, libgcc refers to it but does not define it. > It's defined in libc. > > I stumbled across this trying to link some freestanding > ARM code using the native cross-compilers. The link > failed if I used -nostdlib because of a handful of symbols > such as this. > > Tim I do not know how embedded architectures split it these days and I am not even sure if we have an official ARM port in FSF GCC, but in general these belong in static portion of libgcc.a. If you'd look at bmake glue in gnu/lib/libgcc, you will see that building of __umodsi was there but was disabled by our arm folks presumably because of switch to our own complete softfloat implementation that happens to be in libc. They probably should not have disabled integer math stuff along with libgcc's incomplete floating point implementation, but I guess they had their reasons. Non-embedded architectures do not do that and for amd64/i386 each GCC import since 3. ensured that libgcc_s.so matched one produced by upstream symbol-by-symbol. -- Alexander Kabaev signature.asc Description: PGP signature
Re: rtld or lang/gcc cannot find libgcc_s.so.1
On Feb 23, 2012, at 9:16 AM, Alexander Kabaev wrote: > On Tue, 21 Feb 2012 21:11:13 -0800 > Tim Kientzle wrote: > >> >> If I understand correctly, the libgcc in base is pretty stripped >> down compared to "regular" libgcc, because most of that >> stuff is in our libc instead. >> > > You understand it a bit wrong, but your conclusions are correct. libgcc > in base is not stripped in any way and is supposed to be identical to > one coming from upstream. So where is __umodsi3 supposed to be defined for ARM? In FreeBSD, libgcc refers to it but does not define it. It's defined in libc. I stumbled across this trying to link some freestanding ARM code using the native cross-compilers. The link failed if I used -nostdlib because of a handful of symbols such as this. Tim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: fifo_listen: fchmod public/pickup: Invalid argument with postfix on today's current
On Sat, Feb 25, 2012 at 8:15 AM, Doug Barton wrote: > On 02/24/2012 21:00, Doug Barton wrote: >> I'm on today's -current (r232126) and I'm getting the error in the >> subject when trying to start postfix. I recompiled 2.9, and then tried >> 2.8 both give the same error. > > Backing out r232055 fixed this. > Hi Doug, sorry for the breakage. It should be related to a behavior change in handling fo_chmod/fo_chown for named pipes due to r232055. Could you try the patch at http://www.trematerra.net/patches/fifo_chmod.patch to see if it fixes your issue with postfix? Thank you -- Gianni ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Loading uart module fails
On Fri, Feb 24, 2012 at 12:22:36PM -0500, John Baldwin wrote: > Try this for fixing the panic. New-bus was not clearing the description > if a device's attach routine failed. Thanks, this patch indeed fixes the panic. ./danfe ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: fifo_listen: fchmod public/pickup: Invalid argument with postfix on today's current
On Sat, Feb 25, 2012 at 2:15 PM, Attilio Rao wrote: > Il 25 febbraio 2012 07:15, Doug Barton ha scritto: >> On 02/24/2012 21:00, Doug Barton wrote: >>> I'm on today's -current (r232126) and I'm getting the error in the >>> subject when trying to start postfix. I recompiled 2.9, and then tried >>> 2.8 both give the same error. > > Did you also rebuilt world? I don't think a world rebuild shouldn't be necessary for that change. > Attilio > > -- > Peace can only be achieved by understanding - A. Einstein > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- “The real damage is done by those millions who want to 'get by.' The ordinary men who just want to be left in peace. Those who don’t want their little lives disturbed by anything bigger than themselves. Those with no sides and no causes. Those who won’t take measure of their own strength, for fear of antagonizing their own weakness. Those who don’t like to make waves—or enemies. Those for whom freedom, honour, truth, and principles are only literature. Those who live small, love small, die small. It’s the reductionist approach to life: if you keep it small, you’ll keep it under control. If you don’t make any noise, the bogeyman won’t find you. But it’s all an illusion, because they die too, those people who roll up their spirits into tiny little balls so as to be safe. Safe?! >From what? Life is always on the edge of death; narrow streets lead to the same place as wide avenues, and a little candle burns itself out just like a flaming torch does. I choose my own way to burn.” Sophie Scholl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD: Marvell 88SX61xx should be 88SE61xx
Hi all, Maybe some spam filters ate my mails so I am replying to current@. Could anyone help to commit it? Regards, Jia-Shiun On Thu, Feb 23, 2012 at 8:57 PM, Jia-Shiun Li wrote: > Hi Alexander, > > I've submitted a PR for this: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=165271 > > could you help to review the patch attached to the PR and check it in? > It only changes strings, not any functionality. > > Regards, > Jia-Shiun. > > On Tue, Mar 29, 2011 at 1:57 AM, Jia-Shiun Li wrote: >> Hi Alexander, >> >> I am Jia-Shiun Li, writing to you for the Marvell SATA device names in >> FreeBSD drivers. >> >> I noticed the boot message for my onboard 88SE6121: >> >> atapci0: port >> 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f mem >> 0xfeaffc00-0xfeaf irq 16 at device 0.0 on pci2 >> ahci0: on atapci0 >> >> according to Marvell their names should be 88SE[69]1xx instead of >> 88SX[69]1xx: >> http://www.marvell.com/products/storage/storage_system_solutions/sata_controllers_pc_consumer/ >> >> a simple way to tell is that mvs(4) devices are 88SX and ahci(4) devices are >> 88SE. >> >> I made a patch out of this, basically just text replacement. It does not >> affect functionality, but I think it would be better to be identified >> correctly anyway. Would you mind help committing the changes? >> >> Regards, >> >> Jia-Shiun. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: fifo_listen: fchmod public/pickup: Invalid argument with postfix on today's current
Il 25 febbraio 2012 07:15, Doug Barton ha scritto: > On 02/24/2012 21:00, Doug Barton wrote: >> I'm on today's -current (r232126) and I'm getting the error in the >> subject when trying to start postfix. I recompiled 2.9, and then tried >> 2.8 both give the same error. Did you also rebuilt world? Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
