Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Aug 2006 00:18:52 +0200
From:      Alexander Leidinger <netchild@FreeBSD.org>
To:        John Baldwin <john@baldwin.cx>
Cc:        cvs-src@FreeBSD.org, src-committers@FreeBSD.org, rwatson@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/i386/linux systrace_args.c src/sys/amd64/linux32 systrace_args.c
Message-ID:  <20060816001852.205718a7@Magellan.Leidinger.net>
In-Reply-To: <200608151250.03860.john@baldwin.cx>
References:  <200608151256.k7FCuaw3086324@repoman.freebsd.org> <200608151250.03860.john@baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
Quoting John Baldwin <john@baldwin.cx> (Tue, 15 Aug 2006 12:50:03 -0400):

> On Tuesday 15 August 2006 08:56, Alexander Leidinger wrote:
> > netchild    2006-08-15 12:56:36 UTC
> > 
> >   FreeBSD src repository
> > 
> >   Added files:
> >     sys/i386/linux       systrace_args.c 
> >     sys/amd64/linux32    systrace_args.c 
> >   Log:
> >   add autogenerated systrace_args stuff for dtrace
> 
> These should probably be renamed to linux_systrace.c, etc. like the other 
> files to avoid collisions of systrace_args.o during a kernel build.  This is 
> not a linux-specific issue though as when systrace_args was added only 1 of 
> the 9 system call tables in the kernel were regenerated.

I didn't added them to the build, only to the repo. If they aren't
added to the build automatically, this isn't an issue for now.

If they are added in some way, someone with more knowledge about this
dtrace stuff should have a look at it. It may be the case, that just
adding 'systrace="linux_systrace_args.c"' to syscalls.conf isn't
enough, I don't know.

Bye,
Alexander.

-- 
      ...and that is how we know the Earth to be banana-shaped.
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org     netchild @ FreeBSD.org  : PGP ID = 72077137



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060816001852.205718a7>