On Thu, May 16, 2002 at 06:17:44PM -0600, Lyndon Nerenberg wrote:
> > "Ade" == Ade Lovett <[EMAIL PROTECTED]> writes:
>
> Ade> Because not everyone using the ports system has the in-place
> Ade> editing feature of sed that was recently added, and thus it
> Ade> needs to be conditi
>perl -pi.hold -e 's/FOO/BAR/g' ${WRKSRC}/a/b/{X,Y}
> is not as easy to do with `ed'.
It's not *that* hard. 10 lines of shell script is preferable to
XX MB of perl bloat. Especially for this sort of problem.
--lyndon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
[bogus From: address, because people cannot be bothered to respect Reply-To:]
On Thu, May 16, 2002 at 06:17:44PM -0600, Lyndon Nerenberg wrote:
> Why can't we use ed for in-place edits?
perl -pi.hold -e 's/FOO/BAR/g' ${WRKSRC}/a/b/{X,Y}
is not as easy to do with `ed'.
People should find so
On Wed, May 15, 2002 at 09:31:11AM +0300, Ruslan Ermilov wrote:
> This actually doesn't affect only cross-arch case, the subject is wrong.
> It affects any arch with HOST_BITS_PER_WIDE_INT > HOST_BITS_PER_LONG e.g.
> alpha.
This *is* only a cross issue.
HOST_BITS_PER_WIDE_INT == HOST_BITS_PER_LON
> "Ade" == Ade Lovett <[EMAIL PROTECTED]> writes:
Ade> Because not everyone using the ports system has the in-place
Ade> editing feature of sed that was recently added, and thus it
Ade> needs to be conditional on ${OSVERSION}.
Why can't we use ed for in-place edits?
--lyndon
To
We have started a "ALTQ integration in FreeBSD" project which is
headed towards integrating Mr. Kejiro's ALTQ framework into FreeBSD
5.0-current (and perhaps 4-stable later). The FreeBSD Core Team has been
advised and we have received on principle approval. We are looking
for help with committ
On Thu, May 16, 2002 at 05:52:45PM -0500, Ade Lovett wrote:
> On 05/16/02 17:46, "Maxime Henrion" <[EMAIL PROTECTED]> wrote:
> > I agree that a __FreeBSD_version bump is appropriate, but why not always
> > simply use sed for this ?
>
> Because not everyone using the ports system has the in-place
On 05/16/02 17:46, "Maxime Henrion" <[EMAIL PROTECTED]> wrote:
> I agree that a __FreeBSD_version bump is appropriate, but why not always
> simply use sed for this ?
Because not everyone using the ports system has the in-place editing feature
of sed that was recently added, and thus it needs to b
Ade Lovett wrote:
> Could we have a __FreeBSD_version bump for the diking out of perl from the
> base system please? A chunk of ports work needs to be done to conditionally
> use perl vs sed for in-line replacements on lots of Makefiles.
I agree that a __FreeBSD_version bump is appropriate, but
Could we have a __FreeBSD_version bump for the diking out of perl from the
base system please? A chunk of ports work needs to be done to conditionally
use perl vs sed for in-line replacements on lots of Makefiles.
Thanks,
-aDe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscrib
On Thu, May 16, 2002 at 06:47:39AM -0400, Thomas David Rivers wrote:
>
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > RS/6000's didn't used to use PPC processors at all; so it's
> > probably intentional software compatability.
>
> I'm confused then - the one we have here seems to. There
> was
> "Warner" == Warner Losh <[EMAIL PROTECTED]> writes:
Warner> H, I've found that the Intel PRO/Wireless are 5.0V devices.
Warner> Maybe this is a different card than what I'm used to dealing
Warner> with.
>From the reseller, this is the main difference beetween 2011 & 2011b
(chipset d
Dag-Erling Smorgrav writes:
> make: don't know how to make style.perl.7. Stop
> *** Error code 2
This was fixed a few hours ago.
Drew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, May 16, 2002 at 09:07:25AM +0300, Ruslan Ermilov wrote:
> it's possible to achieve this with:
>
> : make \
> : -DNO_worldtmp -DNO_bootstrap-tools -DNO_cleanobj -DNO_obj \
> : -DNO_build-tools -DNO_cross-tools \
> : buildworld TARGET_ARCH=foo
>
> Which in essence is equivalent
> Sounds like you should forward this to [EMAIL PROTECTED] :-)
> CC audit@ (and current@) so we can all see what the GNU people say.
> Don't forget to show the output of `cc -v'.
knu has already created a gnats pr with gcc and posted the url.
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree
On Thu, May 16, 2002 at 12:06:49PM -0700, Bill Fenner wrote:
> >Specifically what is the problem? Given the program below, take the
> >ISO-C spec and explain the problem. Or even w/o the spec -- I haven't
> >been reading this thread.
>
> > > int
> > > main()
> > > {
> > >unsigned char i = 1
>Specifically what is the problem? Given the program below, take the
>ISO-C spec and explain the problem. Or even w/o the spec -- I haven't
>been reading this thread.
> > int
> > main()
> > {
> >unsigned char i = 127;
> >char j;
> >
> >printf("%d\n", ((char)(i << 1)));
This print
On Thu, May 16, 2002 at 08:31:19PM +0900, Akinori MUSHA wrote:
> > > So - yes - it seems gcc 3.1 does have a problem...
> > Indeed - easily determined by breaking down the expression.
> > So, who's gonna report it to gcc-bugs? knu?...
Specifically what is the problem? Given the program below, t
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
I've submitted a bug report to GCC GNATS:
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&pr=6677&cmd=view+audit-trail
Let's see how they handle this.
--
/
/__ __Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org
On Thu, May 16, 2002 at 01:14:01PM -0400, Mike Barcroft wrote:
> Riccardo Torrini <[EMAIL PROTECTED]> writes:
> > # cd /usr/ports/emulators/bochs && make
> > [...]
> > gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev'
> > [...]
> > c++ -c -O2 -pipe -march=pentiumpro -f
Riccardo Torrini <[EMAIL PROTECTED]> writes:
> # cd /usr/ports/emulators/bochs && make
> [...]
> gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev'
> [...]
> c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions
> -fomit-frame-pointer -I/usr/X11R6/include -I
At Thu, 16 May 2002 21:58:56 +1000 (EST),
Bruce Evans wrote:
> > Somehow, specifying -fsigned-char, which I thought was the default,
> > fixed the problem. So, the cause may be in our configuration of gcc?
>
> -fsigned-char doesn't fix it for me. Neither does repacling "char" by
> "signed char"
On 16-May-2002 Dag-Erling Smorgrav wrote:
> John Baldwin <[EMAIL PROTECTED]> writes:
>> e -n 100
>
> Yep, this (well, e -w -n 100 blah, and a number of variations) is what
> I tried.
This works on my PWS 500au but not on the DS20.
>> e -n 100 vmem:
>
> I guess the address space specifier is
¿¬¾Ö¶õ ³²ÀÚ°¡ ´Ü ÇÑ »ç¶÷ÀÇ ¿©ÀÚ¿¡ ¸¸Á·Çϱâ À§ÇØ Ä¡·ç´Â ³ë·ÂÀÌ´Ù. -Ç® Á¦¶ó¸£µð
±¸Çؼ ¾òÀº »ç¶ûÀº ÁÁÀº °ÍÀÌ´Ù. ±×·¯³ª ±¸ÇÏÁö ¾Ê°í ¾òÀº °ÍÀº ´õ¿í ÁÁ´Ù. -¼ÎÀͽºÇǾî
»ç¶ûÇÏ´Â °ÍÀÌ ÀλýÀÌ´Ù. ±â»ÝÀÌ ÀÖ´Â °÷¿¡ »ç¶÷°ú »ç¶÷ »çÀÌÀÇ °áÇÕÀÌ
¹ÞÀ¸½Ã´Â ºÐ²² ÇÊ¿äÇÑ Á¤º¸°¡ µÇ±æ ¹Ù¶ó¸ç º¸³»µå¸³´Ï´Ù.
±×·¸Áö ¾
On Thu, 2002-05-16 at 05:42, Hans Lambermont wrote:
> Is anyone else able to upgrade from stable to current ?
I'm running current, and I'm experiencing the same problem you are.
--
Michael D. Harnois bilocational bivocational
Pastor, Redeemer Lutheran ChurchW
On Thu, 16 May 2002, Akinori MUSHA wrote:
> [CC: obrien, who has been working on bringing in gcc 3.1]
>
> At Wed, 15 May 2002 20:46:06 -0700,
> Bill Fenner wrote:
> > So, who's gonna report it to gcc-bugs? knu?...
> >
> > int
> > main()
> > {
> >unsigned char i = 127;
> >char j;
> >
> >
[CC: obrien, who has been working on bringing in gcc 3.1]
At Wed, 15 May 2002 20:46:06 -0700,
Bill Fenner wrote:
> > So - yes - it seems gcc 3.1 does have a problem...
>
> Indeed - easily determined by breaking down the expression.
>
> So, who's gonna report it to gcc-bugs? knu?...
>
> int
>
Terry Lambert <[EMAIL PROTECTED]> wrote:
> Thomas David Rivers wrote:
> > Well - it's not counter-intuitive on many machines... For example,
> > on the IBM mainframe - there is an instruction to load a character
> > into a register - but not one that loads *and* sign-extends. So,
> > you can
more info on this problem:
Hans Lambermont wrote:
> cd /usr/src; make buildincludes; make installincludes
> make: don't know how to make buildincludes. Stop
I found the buildincludes target in share/mk/bsd.incs.mk
These mk files should have been used (
MAKE= PATH=${PATH} make -m $
# grep BOCHS /etc/make.conf
WITH_BOCHS_CPU_LEVEL= 6
WITH_BOCHS_PROCESSORS= 1
# uname -v
FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 [...]
# cd /usr/ports/emulators/bochs && make
[...]
gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev'
[...]
c++ -c -O2
On Wed, 15 May 2002, John Baldwin wrote:
> On 15-May-2002 Dag-Erling Smorgrav wrote:
> > John Baldwin <[EMAIL PROTECTED]> writes:
> >> The kernel overflowed it's stack. In SRM, you can try to debug this
> >> by using 'e sp' to get the stack pointer then get a stack dump and save
> >> a copy of i
Dear Giorgos,
Thanks for your suggestion! The problem has gone away by
backing off to -O1 in kernel and -O2 in userland. Strange,
because I have been using -O3 -fomit-frame-pointer for a
while now (/usr/share/examples/etc/make.conf notwithstanding)
with ill effects. My bad.
Sorry, but I can't
John Baldwin <[EMAIL PROTECTED]> writes:
> e -n 100
Yep, this (well, e -w -n 100 blah, and a number of variations) is what
I tried.
> e -n 100 vmem:
I guess the address space specifier is what was missing.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PR
34 matches
Mail list logo
