Accepted:
libbsd-dev_0.2.0-1_amd64.deb
to main/libb/libbsd/libbsd-dev_0.2.0-1_amd64.deb
libbsd0-dbg_0.2.0-1_amd64.deb
to main/libb/libbsd/libbsd0-dbg_0.2.0-1_amd64.deb
libbsd0-udeb_0.2.0-1_amd64.udeb
to main/libb/libbsd/libbsd0-udeb_0.2.0-1_amd64.udeb
libbsd0_0.2.0-1_amd64.deb
to main/li
Hi!
On Wed, 2009-12-16 at 17:59:23 +0100, Werner Koch wrote:
> On Wed, 16 Dec 2009 16:09:19 +0100, Guillem Jover wrote:
> > I was in the process to release a new upstream release for libbsd, and
> > can include those functions. I'll then proceed with an upload to
> > Debian.
>
> Find below a patc
libbsd_0.2.0-1_amd64.changes uploaded successfully to localhost
along with the files:
libbsd_0.2.0-1.dsc
libbsd_0.2.0.orig.tar.gz
libbsd_0.2.0-1.debian.tar.gz
libbsd-dev_0.2.0-1_amd64.deb
libbsd0_0.2.0-1_amd64.deb
libbsd0-udeb_0.2.0-1_amd64.udeb
libbsd0-dbg_0.2.0-1_amd64.deb
Greeting
Hi,
> And fixed ;-)
In time before big-endians appear. :))
> > - Is kernel module atapicam enabled by default ?
> Bundled in,
Good decision.
> attached is whole config.
I will have to learn reading it.
> > - Are ACL enabled for individual filesystems by
> To be honest, we have deeper probl
Followed the install through the return out of Alt-F3 back to Freebsd
sysinstall. Instructions didn't mention any additional steps once back to
sysinstall. Exited out. At boot the system comes up to a command line login.
Entered root and the root prompt comes up without asking for passwd. That m
Hi,
Petr Salinger wrote:
> Please note that
> libisofs/builder.c:209: warning: passing
> argument 2 of 'aaip_cleanout_st_mode' from
> incompatible pointer type
> is not problem in your code. Your code only detected
> problem in our code ;-)
I understand the warning is harmless for little
endia
I have tried to react on the warnings of buildd
on kfreebsd. The release is planned to come soon.
Please note that
libisofs/builder.c:209: warning: passing
argument 2 of 'aaip_cleanout_st_mode' from
incompatible pointer type
is not problem in your code. Your code only detected
problem in ou
The code in question is:
unsigned thread::hardware_concurrency()
{
#if defined(PTW32_VERSION) || defined(__hpux)
return pthread_num_processors_np();
#elif defined(_GNU_SOURCE)
return get_nprocs();
It seems that get_nprocs() is always implemented by Glibc. Worst-case i
8 matches
Mail list logo