etter to have it fail when somebody does
use a different compiler. I think the discussion that it will trigger
will yield a less gratuitous convention. Possibly documented. YMMV.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ct, but now it also has
-lc_r explicitly. Again, this can result in a bad shared object.
I don't think there's a bug.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
eally is :-)
> Since ia64 is
> a -CURRENT only architecture, your explanation makes me think using
> -lc_r explicitly in -CURRENT is still a bad idea.
Yes. We have the same problem with libobjc.a that's being linked into
a shared object (ports/lang/gnustep-base). The problem is not eas
o reorganize your sources in
order to use bsd.prog.mk or enhance the BSD includes to deal
with that (if appropriate).
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
egin with, and has a new fix now:
> > Re: kern/23173: read hangs in linux emulation
> > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173
>
> Assigned to maintainer.
I'm not the maintainer, but I'll commit the patch in a couple of longish
minutes. An MFC will hap
don't know about,
o Declare all these syscalls as dummies (see linux_dummy.c) to begin
with,
o Really implement those syscalls that are used in practice.
Syscall 252 is exit_group(2).
FYI,
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
__
x. It therefore
makes the problem larger, not smaller.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sides the technical
divergence it also seems to have the effect of purifying the FreeBSD
community from those who are dumb enough to make a fool of themselves,
and indirectly the project, race and species they're associated with
or otherwise belong to. Unfortunately, that's still 2
very
> bad technical decisions have been made over the last few years (Hence
> DragonFly's existence).
I don't think it's that bad or that it can be generalized this way,
but there are some examples that seem to support what you say.
--
Marcel Moolenaar USPA: A-39004
e hardcoded the message type to 0.
[EMAIL PROTECTED] is the maintainer of linprocfs. You may want to ping
him more directly.
PS: please break lines around 70 characters or so. It makes your mail
so much better to read.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To
ight?
See i386/33300. Gordon stacked it on my plate. I'm very much focussed
on getting FreeBSD/ia64 in a releasable state so I might not get to
it soon, but it'll be done... eventually :-)
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ibility. I think I'm going
to borrow a thought or two from Linux which allows further increasing of
the number of signals without rewriting the logic, but that's basicly
undecided yet and open for discussion.
--
Marcel Moolenaar mailto:[EMAIL PROTECTED]
S
sigset_t in
the kernel without recompilation of userland tools.
--
Marcel Moolenaar mailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
Amsterdam, The Netherlands tel: +31 20 4200655
To Un
Sheldon Hearn wrote:
>
> On Mon, 30 Aug 1999 15:55:56 +0200, Marcel Moolenaar wrote:
>
> > The Linux trick I like to add is to have sigset_t always be the last
> > field in structures so that the impact of enlarging sigset_t is
> > minimal.
>
> On LITTLE_ENDIAN
worth having __sigbits to be the size that most suits the architecture (32
for i386; 64 for alpha) because of the frequent bit manipulations that are
expected to be performed with it?
--
Marcel Moolenaar mailto:[EMAIL PROTECTED]
SCC Internetworking & Da
t; < libosl516li.so.bak > libosl516li.so
> > > touch /compat/linux/so
> >
> > I don't think this one is needed anymore ?!?
>
> It is. Without it, soffice keeps bringing up setup over and over instead
> of just starting the damn office.
Wh
Mikhail Teterin wrote:
>
> Marcel Moolenaar once wrote:
>
> > > >
> > > > I don't think this one is needed anymore ?!?
> > >
> > > It is. Without it, soffice keeps bringing up setup over and over
> > > instead of just starti
Vince Vielhaber wrote:
>
> On Thu, 2 Sep 1999, Mikhail Teterin wrote:
>
> > Marcel Moolenaar once wrote:
> >
> > > > >
> > > > > I don't think this one is needed anymore ?!?
> > > >
> > > > It is. Without it, soffi
[EMAIL PROTECTED] wrote:
>
> On Thu, 2 Sep 1999, Marcel Moolenaar wrote:
>
> > SO5.1 installs OOTB on both -current and -stable. I suspect your -stable is
> > not recent?
>
> Is this true for BOTH versions of the tarball? Changes where made to the
> distributio
; requires jumping throught the hoops (unzip setup.zip, etc.) to
> install but runs OOTB after that. I havn't tried to do a
> 'network' install.
Sigh...
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://w
ways needed to do. It can't find the shared object because
it simply is not in a searchable place. Setting LD_LIBRARY_PATH solves it.
I always thought it was related to setting TMP to /var/tmp because I don't
have enough space on /.
--
Marcel Moolenaarmailto:
s_status.c 1999/08/28 00:46:56 1.16
+++ procfs_status.c 1999/09/04 06:32:46
@@ -199,6 +199,7 @@
ps += done;
bytes_left -= done;
}
+ ps--;
}
else {
ps = psbuf;
Thanks,
--
Marcel Moo
Hi,
Another issue when sigset_t changes is the version numbers of shared
libraries. Since libc and libc_r have changed on the interface level, they
need a version bump. I assume that all others automaticly also need a
version bump then. Am I correct in this assumption?
--
Marcel Moolenaar
es.
> For GCC, __asm__ attribute also can be used.
That still is an interface change and thus needs a version bump. How else
do I know wich version x library has the new implementations (besides the
larger one :-)?
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internet
Dmitrij Tejblum wrote:
>
> Marcel Moolenaar wrote:
> > > I suggest to try to avoid the version bump. NetBSD-like way to do it:
> > > Give new implementations another names in object files, so that they
> > > don't conflict with old implementations, and pre
everything" and noone, I hope, will use such dlsym.
Your suggestion has more impact than that. It violates POLA. In all case a
certain function is called `foo' except in the library where it resides,
where it is called `bar'. I can imagine programmers to get really confused
when th
ies but the latest with a given major version...
Ah, well... so much for this brainwave :-)
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsu
called `foo' except in the library where it resides,
> > where it is called `bar'. I can imagine programmers to get really confused
> > when their linker starts complaining about function `bar' and they simply
> > can't find a reference to `bar' in their
ery library that has changed directly or
indirectly for this scheme to work.
Now, are you going to do the reimplementation for every library on this
planet just to prevent someone from recompiling his library and forgetting
to reimplement those functions that got changed indirectly *without he even
knowing that something has changed*? Are you the one that does the
debugging to find out exactly what has gone wrong? What are the changes of
finding the problem?
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Richard Wackerbarth wrote:
>
> On Thu, 09 Sep 1999, Marcel Moolenaar wrote:
> > Sheldon Hearn wrote:
>
> > I'm more tempted to revert to the major/minor versioning. Every change
> > triggers a minor version bump, but only if the library is still backwards
> &g
o,
if you got something to say, say it now.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &qu
ur solution can maintain a higher degree of compatibility
then a version dump. In both cases you can run -stable binaries on -current
but not the other way around.
> [perhaps, I will answer the rest of your mail later]
I do hope so. I think that adding functions to hide datatype changes have
user perspective, is salvaging not also important?
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
cage
And let the client specify /cage/tmp/client.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
nstallation ) or are all the packages going to
> be recompiled to use the new version numbers ( including X )
The libraries should probably be added to compat3x, yes.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases
e this is the case?
> [but you can't build world until you booted a new kernel, and you
> can't boot a new kernel until you have a new loader, but you can't
> build a new loader...]
This is "artifical" in that it is solved by fixing the build process.
ing every Linux app from to
> .
soundcard.h has been moved by Peter from machine/ to sys/. A commit logs
tells us:
\begin{quote}
-> , since it's an exported API
that's arch neutral and OSS API and Linux API compatable.
\end{quote}
The link is to prevent breakages. Use #include in
t; way is to fix this.
Make sure int32 is not defined in terms of long. If it is, then bp_xid
is aligned on a 8 byte boundary adding 4 bytes to the size of the
struct. Since long if 64-bits on the Alpha, the total increase will be
8. Any alignment at the end of the structure shouldn't cause
ilinglists very closely, so I may have missed a
couple of patches already...
Thanks,
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubs
e identical, there's no reason for the code to be
there. Very confusing :-)
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]
To Unsubscribe: send
Christian Bruno wrote:
> I know that Oracle 8.0.5 Linux can run on FreeBSD, and i cant imagine such
> an application do not use the /proc
Oracle doesn't use /proc.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases ht
on.
> 4. Build the world's binaries.
> 5. Process anything in /usr/share or other places that requires
> the use of those binaries, using the OBJECTS compiled in step (4).
This won't work if you're cross-building.
--
Marcel Moolenaar
ously.
>
> This would appear to be another thing Marcel has broken..
>
> colldef used to have special treatment, but it no longer has.
Fixed thanks. I actually had it in my -stable to -current tests, but
somehow got lost while committing it.
--
Marcel Moolenaar
ng
> run, but the concepts are similar (programs and thier arguments).
Correct. The for-loop is expanded before any targets are made. That's
why the normal use of SUBDIR is non-parallel; it's used in a for-loop.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Inter
101 - 144 of 144 matches
Mail list logo
