Hello.
Is it possible to build Eclipse (and other java ports)
with openjdk6/7?
I have both built and installed but for whatever reason,
attempting to build Eclipse always causes the ports system
to try to build jdk16 as a dependency (which fails as it's
an "interactive port" and I always run in B
Hello.
What's the current status of DRI/3D support with the 4xxx range of ATI
cards?
I'm on 8.0-RELEASE and have just installed a (borrowed) 4870 card. I
get working dual monitor support but only software rasterization in
xorg.
The intention is to replace a broken x1950 card with something at le
Ok, here's where I am with this.
I'm currently using the Audiophile for the sake of simplicity (I'm assuming
that if the Audiophile works properly, the Delta 66 probably will too).
/dev/sndstat, at maximum verbosity, looks like:
FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64)
Installed dev
On 2010-07-22 16:32:56, Stanislav Sedov wrote:
> Hi, xw!
>
> I have Audiophile 2496, and it works great for me including the mixer.
> Do you know where exactly these messages come from?
>
Hi.
It seems to be when /etc/rc.d/mixer attempts to restore mixer settings
on boot.
I took the cards out,
So, anyway, I have both an Audiophile 2496 and a Delta 66 card that
I can send to any developer interested in getting them working (ideally
I'd like them back some day).
Is there anyone interested in fixing these drivers?
Bare in mind I have no idea how much work this is. The audio subsystem
seem
On 2010-07-07 22:50:14, pluknet wrote:
>
> Hi!
>
> I have audiophile192 card, it uses a different envy24ht (not envy24),
> but with the same mixer warnings you described above.
> I saw these warning since time driver has been committed to the tree.
Hi,
Does the card actually work?
Can you get
Hello.
Is anyone using the envy24 audio driver?
I've tried it with two cards (M-Audio Delta 66, M-Audio Audiophile)
and it just doesn't work properly. Both are claimed to be supported
and yet they spew errors to the console on boot:
WRITE_MIXER: Device not configured
WRITE_MIXER: Device not conf
Hi.
I've had two people tell me that this is supposed to be working
these days (8.0-RELEASE-p2) but I'm not having much luck.
I have a 32 bit chroot, built with "make buildworld TARGET=i386"
and have built a pile of ports in that jail (i386 libGL, i386
dri, etc, etc).
I've tried running the chro
When compiling some QT4 based programs from source, the configure
script asks for $QTDIR.
On Debian and other systems, there's a single QT root with symlinks
to the real locations:
$ ls -alF /usr/share/qt4/
total 356
drwxr-xr-x 6 root root 4096 2010-05-05 15:01 ./
drwxr-xr-x 187 root root 4
'Lo,
On 2010-03-13 20:40:32, jhell wrote:
> Not that this is a solution to your problem but it might be a possibility
> for you to consider, but a couple years back I dropped using make
> package(-recursive) and just scripted out making backup packages using
> something like the following.
I p
> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
> rest of the paths with their defaults that are relative to PORTSDIR? If
> that works, then we can start hunting for places that are not handling
> absolute vs. relative paths correctly in bsd.port.mk.
Now, with only:
PORT
On 2010-03-12 22:36:54, Greg Larkin wrote:
> Hi xw,
>
> I noticed something strange here. How is WRKDIR (in this case
> "/var/ports/work/var/ports/tree/devel/eggdbus/work") defined? It looks
> like bsd.port.mk combined your WRKDIRPREFIX and PORTSDIR to create that
> path, but skimming the code,
This is a complete lot of how to reproduce the various errors I've
seen with 'make package-recursive'. I've checked the pointyhat logs
and there are no errors logged for the packages involved here. There
seems to be a bug somewhere in ports. I've used inkscape as a scapegoat
here but the errors occ
'Lo.
As a test, I've now stripped nullfs out of the picture entirely. The
exact same problem still occurs:
Creating package /pkg/All/libgpg-error-1.7.tbz
Registering depends: gettext-0.17_1 libiconv-1.13.1_1.
Creating bzip'd tar ball in '/pkg/All/libgpg-error-1.7.tbz'
rmdir: /work/ports/security/
'Lo,
On 2010-03-05 09:47:11, jhell wrote:
> Adding on to this. There were reports in various cases dating back to ~1
> year with bad results, possible data loss, hard and soft dead locks when
> nullfs was used with ZFS. nullfs at one point that I do remember was not
> recommended to be used at all
So, anyway...
Is there any resolution for this problem?
I have quite a few packages I'd like to get built (just "custom"
enough that pre-built packages from FreeBSD mirrors won't suffice).
I have to admit to not being convinced that nullfs is at the root
of the problem... I have vague, confused
'Lo,
Here's the current state of '/work':
http://coreland.ath.cx/tmp/work.txt
On 2010-03-01 20:08:45, Dag-Erling Smørgrav wrote:
> That's begging the question... Clearly you're using nullfs because you
> need something done that you think nullfs can do for you. I'd like to
> know what that i
On 2010-03-01 15:10:16, Dag-Erling Smørgrav wrote:
> xorquew...@googlemail.com writes:
> > There's certainly no parallel building going on, but /work is nullfs
> > mounted (from ZFS). Could this cause the above?
>
> Not sure. Why are you using nullfs?
Basically because "I don't know any better".
On 2010-03-01 14:34:50, Dag-Erling Smørgrav wrote:
> % fgrep 'Directory not empty' inkscape.txt
> rmdir: /work/ports/devel/boost-libs/work: Directory not empty
> rmdir: /work/ports/x11-toolkits/gtkmm24/work: Directory not empty
> rmdir: /work/ports/devel/boehm-gc/work: Directory not empty
> rmdir:
On 2010-02-26 17:38:00, Greg Larkin wrote:
> Can you post a full log file of the process somewhere? The best way to
> capture it is with the commands:
'Lo,
I did actually send a log in response to DES' email but I sent the email
from the wrong account and it still awaits list moderation.
Here i
> cd $port
> make clean
> make deinstall
> make depends # just to be safe
> make install
> make package-recursive
This apparently didn't solve the problem (same errors).
I'm stumped.
xw
___
freebsd-hackers@freebsd.org mailing list
http://lists
'Lo,
On 2010-02-26 12:39:26, Greg Larkin wrote:
> "make package-recursive" calls "make package-noinstall" for all of the
> dependent ports. I'm assuming that means that the dependent packages
> all have to be installed first, so I would change your script like so:
>
> cd $port
> make clean
> mak
'Lo.
I've come up against an infuriating problem with ports. I don't even
know what causes it, let alone how to solve it.
Essentially, to stop already-installed software from polluting port
builds, I build ports in a jail. I put a list of ports in a file and
use a trivial shell script to build th
On 2009-12-01 09:32:56, Alexander Leidinger wrote:
>
> My workaround with MySQL is to have the jail and the socket in the
> same FS (I would prefer to have them on separate FS). Then you can do
> a hardlink of the socket into the jail (obviously after each restart
> of the software, but this
On 2009-11-30 15:43:01, Ivan Voras wrote:
> xorquew...@googlemail.com wrote:
> > 76030 initial thread STRU struct sockaddr { AF_LOCAL,
> > /tmp/jack-11001/default/jack_0 }
> > 76030 initial thread NAMI "/tmp/jack-11001/default/jack_0"
> > 76030 initial thread RET connect -1 errno 61 Connect
jackd (audio/jack) creates a directory in /tmp with a UNIX domain socket
in it. Clients connect to this socket to communicate with the server.
$ jackd -d oss -r 44100 -p 128
$ ls -alF /tmp/jack-11001/default
total 4
drwx-- 2 xw wheel 512 30 Nov 14:19 ./
drwx-- 3 xw wheel 512 30 Nov 1
It seems that the only way to set the output of uname in
a jail is to define environment variables.
Unfortunately, there doesn't seem to be a reliable way
to unconditionally set them (a process might do the
equivalent of 'env -i /bin/sh' and unset them, etc).
Apart from just patching the uname ut
On 2009-11-19 17:12:19, Sam Fourman Jr. wrote:
>
> I would like to help get this working.. is there a howto somewhere to
> setup a i386 jail on amd64?
> I used teh instructions on http://wiki.freebsd.org/Wine (and pointed
> the jail to /compat/i386)
> Inside teh jail uname -a still produces this:
On 2009-11-19 12:15:18, Kostik Belousov wrote:
> On Thu, Nov 19, 2009 at 09:36:54AM +, xorquew...@googlemail.com wrote:
>
> It is in 8.0.
Excellent, thanks.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
On 2009-11-19 11:25:48, Kostik Belousov wrote:
> > I'm using 7.2-RELEASE-p4 here.
>
> Required syscalls only implemented in 8/HEAD.
Ah, thanks.
I assume they won't have made it into 8.0-RELEASE when it shows up?
xw
___
freebsd-hackers@freebsd.org mail
On 2009-11-19 11:03:41, Kostik Belousov wrote:
>
> You forgot to note the version of the kernel you use.
I'm using 7.2-RELEASE-p4 here.
xw
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubsc
On 2009-11-18 23:19:14, Julian Elischer wrote:
>
> Wine is an exceptional bit of software, in many ways.
> One way it is exceptional is that it uses the system in a number of
> ways that nothing else does. For example it sets various special
> segment register settings and defines several differen
Hello.
I've done a lot of reading on this problem and don't understand why what I have
doesn't work.
http://wiki.freebsd.org/Wine
I have an entirely 32 bit jail, created by cross-compiling the world with
TARGET=i386 and creating a jail from DESTDIR.
The jail appears to be fully functional - a
Status update:
http://gcc.gnu.org/ml/gcc-patches/2009-07/msg00102.html
I replied to the last email in the thread but haven't
heard back yet. Presumably I'll be maintaining the FreeBSD
x86_64 port.
I'm about to start work on the FreeBSD port now.
___
f
On 2009-06-29 17:27:40, Daniel Eischen wrote:
> How's this all going?
>
> I'm updating lang/gnat to gnat-2009 right now. In the
> GNAT sources, it has build instructions including how
> to build the cross - see below.
'Lo,
Thanks for the info. GPL 2009 was also on my list, as was
SPARK (apparent
On 2009-06-23 17:47:26, Marcus Reid wrote:
> Hi,
>
> As a side note, freebsd-hackers is not the correct list for this question.
I considered it a hackers@ question due to the large "ZFS is an experimental
feature" warning.
xw
___
freebsd-hackers@freebs
On 2009-06-22 21:28:26, Artem Belevich wrote:
> On Mon, Jun 22, 2009 at 5:31 PM, wrote:
> > ad11: 953869MB at ata5-slave SATA300
> ..
> > ad14: 476940MB at ata7-master SATA300
> > ad16: 476940MB at ata8-master SATA300
> ..
> ># zpool create storage raidz ad11 ad14 ad16
> > I seem to have less s
Hello.
I've got the following hardware setup:
ad10: 76319MB at ata5-master SATA300
ad11: 953869MB at ata5-slave SATA300
ad12: 953869MB at ata6-master SATA300
ad14: 476940MB at ata7-master SATA300
ad16: 476940MB at ata8-master SATA300
ad12 is used as a single-disk pool. ad10 is formatted UFS
On 2009-06-13 01:42:05, Михаил Кипа wrote:
> I need gnat on FreeBSD 7.2 amd64, but in ports it is only for i386 :(. I have
> tired to compile cross compiler under linux, and now I can compile my ada
> programs under linux for FreeBSD, but I can`t compile native amd64 FreeBSD
> gcc.
> Can anybody h
There is one last thing I'd like clarified. From the zpool
manpage:
In order to take advantage of these features, a pool must make use of
some form of redundancy, using either mirrored or raidz groups. While
ZFS supports running in a non-redundant configuration, where each root
vdev is
On 2009-05-31 13:13:24, krad wrote:
> Please don't whack gstripe and zfs together. It should work but is ugly and
> you might run into issues. Getting out of them will be harder than a pure
> zfs solution
Yeah, will be using pure ZFS having read everything I can find on it so far.
I was skeptical
On 2009-05-30 16:27:44, Mike Meyer wrote:
>
> The last bit is wrong. Moving a zfs pool between two systems is pretty
> straightforward. The configuration information is on the drives; you
> just do "zpool import " after plugging them in, and if the mount
> point exists, it'll mount it. If the syst
On 2009-05-30 14:43:54, Mike Meyer wrote:
> On Sat, 30 May 2009 18:52:39 +0100
> xorquew...@googlemail.com wrote:
> > Simple question then as the handbook describes both ccd and gvinum -
> > which should I pick?
>
> My first reaction was "neither", then I realized - you didn't say what
> version o
Hello.
I'm planning to stripe two disks into a RAID0 configuration. As
far as I can tell, my hardware has no hardware RAID support and
therefore I'll be going the software route.
The machine in question is a workstation used to process large
datasets (audio and video) and do lots of compilation.
On 2009-05-22 02:53:22, Stanislav Sedov wrote:
>
> Why not make this compiler to use fresh binutils from cross-binutils
> instead of using systems binutils? This will also allow to support
> newer processor families and architectures. Is it possible to tell
> GNAT where to look for binutils to ass
On 2009-05-21 16:10:18, Stanislav Sedov wrote:
> You can also try using devel/cross-binutils to build cross-tools for
> x86_64-freebsd. Random people reported they're working fine.
Unfortunately, as noted in this thread:
http://marc.info/?l=freebsd-hackers&m=124146166902690&w=2
Using that port
On 2009-05-21 11:20:21, Robert Watson wrote:
> Not really my area, but if you haven't found "make toolchain" and "make
> buildenv" then you might want to take a look. Typically these will be
> combined with TARGET_ARCH=foo, and in your case foo is 'amd64'. The
> former builds the toolchain r
Hi.
How do I compile the system binutils (contrib/binutils) as i386 ->
x86_64 cross utils? That is, binutils that will run on an i386 host but
will produce x86_64 binaries?
I'm trying to produce a bootstrapping compiler for a port and need to
get these working. I've spent a while reading Makefile
On 2009-05-19 09:51:08, Daniel Eischen wrote:
>
> Even so, you shouldn't need a cross-binutils, only a native
> (amd64) binutils. Your port won't be a cross port, but a
> native amd64 port. The native amd64 GNAT will need a native
> binutils, not a cross binutils. The only thing you will have
>
On 2009-05-18 18:36:15, Daniel Eischen wrote:
> Well, I used a newer binutils on sparc when I did the original
> port. Once I built the cross compiler and binutils toolset,
> I was done with it. After the native compiler is built using
> the cross tools, you should be able to rebuild the native
>
On 2009-05-18 18:36:15, Daniel Eischen wrote:
> Hmm, if the system binutils is 2.15, then it should build
> as a cross. You can do a cross build of all FreeBSD - I
> think you just set TARGET="amd64" to build amd64 from
> a different arch. Part of this process should be to
> create a cross binuti
On 2009-05-18 09:48:31, xorquew...@googlemail.com wrote:
> 1. Compile binutils-2.15.
>
> Unfortunately, compiling these as cross-binutils appear to be problematic:
>
> gmake[3]: Entering directory `/root/memfs/c1-bu-obj/gas'
> gcc -DHAVE_CONFIG_H -I. -I/root/binutils-2.15/gas -I. -D_GNU_S
Hi.
After a week off, another update:
I've realised, too late, that I'm using a version of binutils
(2.19) that's incompatible with the system binutils (2.15).
Specifically, assembler code emitted by the native GNAT contains
.cfi_personality directives (and no doubt other things too) that
can't b
On 2009-05-13 20:06:34, Josef Grosch wrote:
> I'm in search for a decent video card.
I had to do the same thing recently. I wanted dual head (2x 1440x800),
3D accelerated, PCI Express, AMD64 capable graphics.
Finally settled on a Radeon x1950, specifically the Powercolor
x1950. The prices vary wi
Just an update.
Finally managed to get the i386 -> amd64 compiler to compile
gcc 4.4.0. It took a few Makefile patches as for some reason,
cross compilation breaks gnatmake.
About to try to get the amd64 compiler to compile itself and
run the test suite.
Added a system-freebsd_x86_64.ads profile
On 2009-05-06 10:57:25, Daniel Eischen wrote:
>
> Back in the day when I did it, it was with gcc-2.7.x or
> gcc-2.8.x I believe. The cross build process with gnat
> was a little different. I couldn't do a normal gnat build,
> which did a bootstrap and then rebuilt the compiler again
> using the b
On 2009-05-04 20:54:46, Daniel Eischen wrote:
> Yes, you can look at my lang/gnat port to find its
> bootstrap compiler. I would recommend making a binary
> bootstrap compiler on the earliest version of FreeBSD
> amd64 as you can. If you use 8.0-current for instance,
> others will not be able to
On 2009-05-04 15:03:32, Daniel Eischen wrote:
> Right, you should be able to do it from either of those,
> but perhaps the freebsd x86 may be easier.
>
> I would use a PREFIX other than /usr/local (or something
> different than whatever your actual PREFIX is) for the
> builds.
>
> I was looking aro
On 2009-05-04 14:44:52, Daniel Eischen wrote:
> Is that your only system (amd64)? I originally
> ported GNAT to FreeBSD x86 from a solaris-sparc32 system.
> I built a sparc-sun-freebsd GNAT cross compiler using
> the native Solaris GNAT binary and its associated
> sources. I also (first) had to c
Hello.
I'm attempting to compile GNAT on AMD64 with an eye to
extending support to the platform (the gnat-gcc43 port
is ONLY_FOR_ARCH=i386).
GNAT obviously requires an Ada compiler to bootstrap.
What are my options here?
I suspect that I need to create an i386 jail to build
a cross compiler but
On 2009-05-01 15:50:38, Alexander Kabaev wrote:
> On Fri, 1 May 2009 20:21:13 +0100
> xorquew...@googlemail.com wrote:
>
> > Hello.
> >
> > Checking back through my sent mail from the DRI thread, this version
> > of -STABLE was checked out and compiled on Fri, 10 Apr 2009 16:42:51
> > +0100.
> >
On 2009-05-01 15:13:08, Alexander Kabaev wrote:
> How recent are your sources? There were a number of bugs introduced and
> then fixed in releng/7.2 and stable/7 and line number you post does not
> match anything interesting in either.
>
> Please make sure you have latest vfs_cache.c file at the l
On 2009-05-01 19:39:43, Attilio Rao wrote:
> 2009/5/1 :
> > Filed under:
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=134142
> >
> > Would be incredibly grateful if somebody in the know could take
> > a look at this.
>
> But, what's the panic message?
>
It's at the bottom:
Fatal trap 12:
Filed under:
http://www.freebsd.org/cgi/query-pr.cgi?pr=134142
Would be incredibly grateful if somebody in the know could take
a look at this.
xw
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
Hello.
After extensive hardware testing, new thermal compound, new case and a
lot of work improving airflow, I'm now confident my new machine is OK
from a hardware point of view (a weeks worth of memory testing, days
of running prime95, temperature monitoring, extensive sessions with
sysutils/stre
Hello.
Just to let everyone know, I'm now coming to the conclusion that
I may be suffering from hardware/thermal problems and that the DRI
driver wasn't actually at fault (but highlighted the problem by
pushing the hardware... harder).
Thanks for the assistance, though.
xw
_
On 2009-04-11 14:11:15, Robert Noland wrote:
>
> Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
> in -STABLE that didn't make it into the pre-release.
Sorry, should've made that clear. It was meant to be -STABLE but it
seems to be calling itself -PRE. Just to clarify, my
On 2009-04-11 16:12:45, Mikolaj Golub wrote:
>
> If you are interested in providing useful information about your freezes,
> please read the following:
Thanks very much. Will be doing all of the above.
___
freebsd-hackers@freebsd.org mailing list
http://
The machine ran for hours, apparently. I ended up going to
bed and leaving it running. Woke up to find it on display
sleep, frozen.
It didn't panic, apparently.
I've included Xorg.0.log and the last few lines of /var/log/messages
but I don't believe they show anything very interesting.
I should
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
>
> If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
> Not doing this will increase drasticaly chances of locking whole system
> and not providing any debug data.
I don't seem to have that sysctl.
You sure that's the correct name?
xw
On 2009-04-10 13:31:33, Robert Noland wrote:
>
> If it is locking the whole system, then a core is really our best shot.
> If you can extract anything useful from xorg.log or setting
> hw.dri.0.debug that also might be of use.
>
> I'm running on 2 cores, but it is possible that some locking issue
Hello.
On 2009-04-10 12:42:48, Robert Noland wrote:
>
> Are you running powerd by chance? I was seeing an issue that seemed to
> be related to powerd. Since I've disabled it on that box, it hasn't
> hung up any more.
I'm not running powerd, no.
>
> As far as drm is concerned, I've been runni
Hello.
Recently bought a new system and am experiencing problems with system freezes.
I think the most likely culprit is DRI. The freezes occur apparently at random.
I've disabled drm.ko and radeon.ko and the system doesn't appear to have frozen
yet.
I'm running 7.2-PRERELEASE (STABLE as of yeste
On 2009-02-18 11:42:00, Maxim Konovalov wrote:
>
> ipfw(8) prob + dummynet(8).
>
Hi. Thanks for the quick response.
Is there, by any chance, an equivalent for PF? I see there's 'ALTQ'
but it looks to be poorly supported (unless I misunderstand). I have
quite a complicated setup here with PF for
Hello.
I want to verify that a program I'm developing works correctly
in poor network conditions (high latency, random packet loss, etc).
I seem to remember reading something once about somebody simulating
these conditions with PF but can't remember where.
Anybody got any ideas about how I could
On 2009-01-18 01:38:12, Garrett Cooper wrote:
>
> I'd check the release notes between 4.2.x and 4.3.x, and see whether
> or not they invalidated a certain lexigraphical part of C++ that was a
> gray area, which could be affecting your compilation. Have you
> possibly discussed this very issue on t
On 2009-01-17 23:07:29, Nate Eldredge wrote:
> I tried a simple example of this in C++ and it works as expected. (I am on
> 7.0-RELEASE/amd64.) So it isn't completely busted, at least.
>
> Can you post an example that exhibits the problem? Ideally, something
> complete that can be compiled and i
On 2009-01-18 07:39:51, Christoph Mallon wrote:
>
> Are more C functions involved? E.g. is the function pointer passed to
> qsort(), which lives in libc, which is not compiled with -fexceptions.
> Look at the stack trace when the exception occurs. In gdb you can use the
> command "catch throw" (sic
Hello.
I have some C code that's compiled with -fexceptions using
the lang/gnat-gcc43 port. I'm on 6.4-RELEASE-p2.
A function c_function in the C code takes a callback as an argument.
I'm passing this function the address of a function ext_function defined
in another language (Ada, to be precise
On 20080927 04:38:53, Colin Percival wrote:
> I missed the beginning of this thread, but looking back in the archives...
>
> 1. I'm very confident that FreeBSD Update is distributing the updated
> libpthread.so.
Right.
> 2. If you run ident on the libpthread.so.2 which FreeBSD Update distributes,
On 20080927 13:15:15, Simon L. Nielsen wrote:
> Errata's are distributed with freebsd-update just like advisories.
>
> Since freebsd-update 2 (the one in the base system) /usr/src is also
> updated if it exists. That said, note that freebsd-update does not
> get's patches from CVS so $FreeBSD$ un
On 20080927 03:59:28, Jeremy Chadwick wrote:
> On Sat, Sep 27, 2008 at 10:17:33AM +0100, [EMAIL PROTECTED] wrote:
>
> The man page for it states that it's a binary updater for pieces in the
> base system, so you looking at your *source* files would indicate
> absolutely nothing, other than when yo
On 20080927 00:07:57, Julian Elischer wrote:
> I'm sure it's there..
> it may be a different problem of course.
>
I don't know... Checking with ident gives:
$FreeBSD: src/lib/libpthread/thread/thr_kern.c,v 1.116.2.1 2006/03/16 23:29:07
deischen Exp $
The patch claims "1.116.2.1.6.1"
Are these
On 20080927 01:06:22, Daniel Eischen wrote:
>
> It's not security related, so I don't know whether it would be in a
> binary update. You should follow the procedure listed in the links
> above.
I'm not sure either. In every description I see of freebsd-update,
there's a claim that it installs "bi
On 20080926 21:43:48, Daniel Eischen wrote:
> On Sat, 27 Sep 2008, [EMAIL PROTECTED] wrote:
>
>> On 20080926 16:43:37, Julian Elischer wrote:
>>> [EMAIL PROTECTED] wrote:
I'm trying to write a client for the jack audio connection kit
(http://jackaudio.org), have hit an apparent bug and am
On 20080926 16:43:37, Julian Elischer wrote:
> [EMAIL PROTECTED] wrote:
>> I'm trying to write a client for the jack audio connection kit
>> (http://jackaudio.org), have hit an apparent bug and am not sure
>
> what revision of FreeBSD?
Ahem, should've mentioned that.
FreeBSD 6.3-RELEASE-p1 #0: We
I'm trying to write a client for the jack audio connection kit
(http://jackaudio.org), have hit an apparent bug and am not sure
who's at fault.
This is the client:
--
#include
#include
jack_port_t *input_port;
jack_port_t *output_port;
jack_client_t *client;
int
main (void)
{
jack_status_t
On 20080904 00:28:40, Manolo Valdes wrote:
> Hi Hackers
>
> reading a thread from this very list i solve my problem trying to debug user-
> land programs.
>
> the problem was gdb-6.1.1 , and the thread point me to use gdb-6.6
> and all my pains went away.
>
> so my question is:
>
> will be GDB
I apologise, I'm completely screwing up today.
My reply to this thread was obviously supposed to go
to [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
> Is anyone else nervous trusting all his programs to have access to all
> his files? Is there already a reasonable solution to this problem?
I suppose it depends what you're after and how much work you're willing
to put in. I can't define "reasonable" but certainly, with a bit of work
somebody co
On 20080716 18:06:34, Xin LI wrote:
>
> Maybe you want DEBUG_FLAGS='-O2 -pipe -fno-strict-aliasing -g'?
>
Ah! Yes, thank you very much.
I had to remove the quotes, of course (for the benefit of anyone
else reading this in future).
xw
___
freebsd-hacker
On 20080716 17:37:58, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> [EMAIL PROTECTED] wrote:
> | Hello.
> |
> | What's the correct way to ensure that ports are built with '-g'
> | and that binaries/libraries created are not stripped? I'm assuming
> | the first one involves set
Hello.
What's the correct way to ensure that ports are built with '-g'
and that binaries/libraries created are not stripped? I'm assuming
the first one involves setting CFLAGS in /etc/make.conf (admittedly,
it's apparently not supported but I'm not building world with this
setting anyway).
The se
On 20080608 22:10:27, Peter Jeremy wrote:
> On 2008-Jun-08 11:32:54 +0100, [EMAIL PROTECTED] wrote:
> >I'm running an openntpd instance on the host machine, which syncs the
> >clock from the pool at pool.ntp.org. From the log output, ntpd claims to
> >be synced and the time does seem to be correct.
On 20080608 19:56:03, Eugene Grosbein wrote:
> On Sun, Jun 08, 2008 at 12:25:00PM +0100, [EMAIL PROTECTED] wrote:
>
> > The problem is that the ntpd in the jail seems to believe that the host
> > clock is out of sync (from what I can gather), even though it isn't.
>
> That's because ntpd won't bl
On 20080608 12:19:23, Steven Hartland wrote:
> I assume as it would effect the entire machine and hence should be run
> on the base machine instead, not the jail?
I think you might've misunderstood.
The ntpd I'm running on the host syncs the clock (and therefore the whole
machine), the ntpd in th
Anybody know why ntpd might not work in a jail?
I'm running an openntpd instance on the host machine, which syncs the
clock from the pool at pool.ntp.org. From the log output, ntpd claims to
be synced and the time does seem to be correct.
I'm then running another openntpd in a jail which doesn't
On 20080514 09:50:52, Kurt J. Lidl wrote:
> Heck, the last time I looked (admitted, a while ago), it didn't
> even enforce column type checking on tables. (Put this string in
> the INT column? No problem!)
They consider it a feature. Nobody knows why.
On 20080226 15:17:24, Tom Evans wrote:
> Running something like 'jexec 1 /bin/sh' won't allow you to allocate a
> tty. If instead you enable sshd inside the jail, and ssh into the jail,
> sshd will allocate you a tty, and everything will work normally.
Hi.
As I mentioned in my first email, the is
On 20080225 14:24:12, Alexander Leidinger wrote:
> Quoting cali clarke <[EMAIL PROTECTED]> (from Sun, 24 Feb 2008
>> Note that also, this problem does NOT occur if you use ssh
>> to enter the jail as I believe ssh handles tty allocation in
>> advance.
>
> You don't give enough info. I assume you t
100 matches
Mail list logo
