> Any chance of getting the Perl build to properly use ${CC} rather than
> hard coding 'cc'? Also a "find . -type f | xargs grep gcc" shows that
> GCC may be called directly also.
OK - I'll look at that.
> This is a problem for cross builds, and using alternate versions of of
> the compiler (sa
On 1 Apr, David O'Brien wrote:
>> > This is fine just to get things working. But please consider Doing It
>> > Right -- that being wrap the definitions of CC, CFLAGS, and PICFLAG with
>> > USE_ICC rather than strew USE_ICC all over the place. For instance:
>> >
>> > /usr/share/mk/sys.mk
>
--- Miguel Mendez <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 01, 2002 at 07:42:59AM -0800, Shizuka
> Kudo wrote:
>
> Hi there,
>
> > I'm having problem with the TI cardbus bridge to
> > recognize PCCARD in "NEWCARD" kernel. I have a
> desktop
> > with TI PCI1250 adaptor and an IBM Thinkpad with
>
Hi,
there are no up to date current snapshots available.
At ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/ the last
snapshot is from 21-Mar-2002
and at
ftp://snapshots.jp.freebsd.org/pub/FreeBSD/snapshots/i386/ the last
snapshot is from 23-Mar-2002 (apparently disk full).
-Wolfram
--
wosch> there are no up to date current snapshots available.
Yes, current 5-current's fixit.flp is flooded. I have an idea how to
fix it (see current@), but sorry I have no time to check that my idea
is good or bad...
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
On Mon, Apr 01, 2002 at 06:08:40PM -0800, Terry Lambert wrote:
> "Crist J. Clark" wrote:
> > > This came up in the first place because it's a cross-envrionment
> > > issue that needs resolving. The "workaround" exists because the
> > > workaround cops out on the cross-environment part of the proc
"David O'Brien" <[EMAIL PROTECTED]> writes:
> so getting an OPIE formatted challenge on RELENG_4 immediately lets
> someone know it is fake and bogus.
I know. I told you it is a bug in the server.
> > the client attempts challenge-response authentication, which is what
> > is used for PAM.
> I
> there are no up to date current snapshots available.
>
> At ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/ the last
> snapshot is from 21-Mar-2002
>
> and at
> ftp://snapshots.jp.freebsd.org/pub/FreeBSD/snapshots/i386/ the last
> snapshot is from 23-Mar-2002 (apparently disk full).
I
On 30 Mär, I wrote:
> I've a kernel from Mar 27 which isn't able to print with my USB printer.
A kernel from today isn't able to print too, but at least usbdevs
doesn't hang anymore.
I haven't checked if moused still causes the box to hang at shutdown.
Bye,
Alexander.
--
We
In message <[EMAIL PROTECTED]>, Alexander Leidi
nger writes:
>On 30 Mär, I wrote:
>
>> I've a kernel from Mar 27 which isn't able to print with my USB printer.
>
>A kernel from today isn't able to print too, but at least usbdevs
>doesn't hang anymore.
go back about 3 weeks in sys/dev/usb and it w
jhay> I'm building the fixit floppy without a populated /dev. That leaves
jhay> enough space open to fit all the rest of the stuff and it shouldn't
jhay> be needed on -current because of devfs. But I haven't tried it. :-)
That is all I want to check it ASAP :-)
-- -
Makoto `MAR' Matsushita
To
On Tue, Apr 02, 2002 at 03:05:40PM +0200, Alexander Leidinger wrote:
> On 30 M?r, I wrote:
>
> > I've a kernel from Mar 27 which isn't able to print with my USB printer.
>
> A kernel from today isn't able to print too, but at least usbdevs
> doesn't hang anymore.
Great! At least I fixed somethi
On 2 Apr, Poul-Henning Kamp wrote:
>>> I've a kernel from Mar 27 which isn't able to print with my USB printer.
>>
>>A kernel from today isn't able to print too, but at least usbdevs
>>doesn't hang anymore.
>
> go back about 3 weeks in sys/dev/usb and it works.
I know, I reported that too. I j
Pierre Beyssac <[EMAIL PROTECTED]> writes:
> On Mon, Apr 01, 2002 at 11:32:07PM +0200, Dag-Erling Smorgrav wrote:
> > Look for VersionAddendum in /etc/ssh/sshd_config (it can be used in
> > ssh_config as well).
> Uh, no, it does not seem to work in ssh_config, only in sshd_config.
Hmm, that needs
matusita> But I don't checked that we can safely remove /dev/* files from
matusita> fixit.flp (sorry, if no one try to do, I'll do it later).
I've confirmed that it makes no problem, so commit it. We get about
40kbytes of free fixit.flp space again.
-- -
Makoto `MAR' Matsushita
To Unsubscribe
Hi,
kern.pre.mk contains
NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${PROF} ${.IMPSRC}
PROFILE_C= ${CC} -c ${CFLAGS} ${WERROR} ${.IMPSRC}
NORMAL_C_NOWERROR= ${CC} -c ${CFLAGS} ${PROF} ${.IMPSRC}
shouldn't this be
NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${.IMPSRC}
PROFILE_C= ${CC} -c ${CFLAGS
On Mon, 1 Apr 2002, Joerg Wunsch wrote:
> fdioctl() historically attempted to determine the "raw" partition
> (`c') of the device in order to read the label. However, the floppy
> driver never really supported UFS-style partitions anyway. This ended
> up in selecting the wrong device for readin
Peter Jeremy <[EMAIL PROTECTED]> wrote:
> I've just finished updating a system to -CURRENT from mid-April
> (just before the DP1 branch). When I try to login, login(8) goes
> into a loop.
I've seen this occasionally for accounts that have either S/Key or
opie (forgot which one it was) enabled.
On Tue, Apr 02, 2002 at 10:31:39AM +0200, Alexander Leidinger wrote:
>
> You can't link native FreeBSD binaries with icc, it tries to link
> against glibc.
Oh that is easy to fix. We can do it in one of two ways.
Show me the exact link line from icc (I want the equivalent to gcc -v).
--
-- Davi
Is there any chance of getting ifc work under FreeBSD, either the way icc
does or producing Linux binaries?
Regards,
Vladimir
--
Vladimir Kushnir - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 2 Apr 2002, David O'Brien wrote:
> Oh that is easy to fix. We can do it in one of two ways.
> Show me the exact link line from icc (I want the equivalent to gcc -v).
We can also tell 'icc' to use our 'ld'.
-Qlocation,ld,/usr/bin
That didn't seem to work to well though as it still tries
"Crist J. Clark" wrote:
> > The problem is that the kldxref deserves to get its own tools
> > build, so that there is a version that works against 5.x code
> > that can be built on 4.x (or NetBSD or Linux or Solaris or
> > whatever).
>
> It builds fine on 4.x as long as you use the correct header
"Crist J. Clark" wrote:
> On Mon, Apr 01, 2002 at 03:07:46PM -0800, Terry Lambert wrote:
> > "Crist J. Clark" wrote:
> > > This whole argument ignores what the real problem is. The really
> > > correct way to handle this is to use the kldxref(8) built in the
> > > 'buildworld' phase. (It's bad for
Alexander Leidinger wrote:
> Hi,
>
> kern.pre.mk contains
> NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${PROF} ${.IMPSRC}
> PROFILE_C= ${CC} -c ${CFLAGS} ${WERROR} ${.IMPSRC}
> NORMAL_C_NOWERROR= ${CC} -c ${CFLAGS} ${PROF} ${.IMPSRC}
> shouldn't this be
> NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR
lock order reversal
1st 0xc02d9b40 eventhandler @ /usr/src/sys/kern/subr_eventhandler.c:163
2nd 0xc4050008 shutdown_post_sync @ /usr/src/sys/kern/subr_eventhandler.c:116
lock order reversal
1st 0xc882cd00 ithread @ /usr/src/sys/kern/kern_intr.c:187
2nd 0xc02aa0e0 allproc @ /usr/src/sys/kern/k
Steven G. Kargl [[EMAIL PROTECTED]] wrote :
> lock order reversal
> 1st 0xc02d9b40 eventhandler @ /usr/src/sys/kern/subr_eventhandler.c:163
> 2nd 0xc4050008 shutdown_post_sync @ /usr/src/sys/kern/subr_eventhandler.c:116
[ ... ]
> I believe the second is known, but the first appears
> to be
On Tue, Apr 02, 2002 at 10:40:08AM +0200, Dag-Erling Smorgrav wrote:
> > Uh, no, it does not seem to work in ssh_config, only in sshd_config.
> Hmm, that needs fixing then.
I have written the following patch, seems to work ok.
Pierre
--- readconf.c.orig Tue Mar 19 14:29:02 2002
+++ readco
On Tue, 2 Apr 2002, Alexander Leidinger wrote:
> Hi,
>
> kern.pre.mk contains
> NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${PROF} ${.IMPSRC}
> PROFILE_C= ${CC} -c ${CFLAGS} ${WERROR} ${.IMPSRC}
> NORMAL_C_NOWERROR= ${CC} -c ${CFLAGS} ${PROF} ${.IMPSRC}
> shouldn't this be
> NORMAL_C= ${CC} -
On Tue, Apr 02, 2002 at 04:45:13PM -0800, Peter Wemm wrote:
> "Crist J. Clark" wrote:
> > On Mon, Apr 01, 2002 at 03:07:46PM -0800, Terry Lambert wrote:
> > > "Crist J. Clark" wrote:
> > > > This whole argument ignores what the real problem is. The really
> > > > correct way to handle this is to u
"Crist J. Clark" wrote:
> On Tue, Apr 02, 2002 at 04:45:13PM -0800, Peter Wemm wrote:
> > "Crist J. Clark" wrote:
> > > On Mon, Apr 01, 2002 at 03:07:46PM -0800, Terry Lambert wrote:
> > > > "Crist J. Clark" wrote:
> > > > > This whole argument ignores what the real problem is. The really
> > > >
There was a Japanese man who went to America for sightseeing.
On the last day, he hailed a cab and told the driver to drive to the airport.
During the journey, a Honda drove past the taxi. Thereupon, the man leaned out of the
window excitedly and yelled, "Honda, very fast! Made in Japan!"
Afte
Quite the thread from hell... ;^)...
Peter Wemm wrote:
> Using buildkernel/installkernel is your biggest mistake. It is no secret
> what I think of those two targets.
I have to agree with this. They are attempts to idiot-proof
something that can't be idiot-proofed, because idiots are so
cunnin
As Bruce Evans wrote:
> BTW, device cloning seems to work wrong for fd:
>
> %%%
> Script started on Wed Apr 3 02:16:43 2002
> ttyp1:bde@besplex:/tmp> ls /dev/fd0c
> ls: /dev/fd0c: No such file or directory
> ttyp1:bde@besplex:/tmp> ls /dev/fd0c
> /dev/fd0c@
> ttyp1:bde@besplex:/tmp> exit
I can
On Tue, 2002-04-02 at 13:35, Joerg Wunsch wrote:
> j@uriah 92% ls -l /dev/fd1*
(...)
> lrwxr-xr-x 1 root wheel4 Apr 2 20:34 /dev/fd1c@ -> fd0
Uh?
--
brandon s allbery [openafs/solaris/japh/freebsd] [EMAIL PROTECTED]
system administrator [linux/heimdal/too many hats] [EMAIL PROTEC
On Tue, Apr 02, 2002 at 10:52:07PM -0800, Terry Lambert wrote:
> Quite the thread from hell... ;^)...
This is nuthin'. But one reason it continues is...
> Peter Wemm wrote:
> > Using buildkernel/installkernel is your biggest mistake. It is no secret
> > what I think of those two targets.
>
> I
Hi all...
I am running a very recent -CURRENT. Within X, running w produce weird
message:
$ w
w: /dev/:0: No such file or directory
2:52PM up 40 mins, 2 users, load averages: 1.52, 1.73, 1.42
USER TTY FROM LOGIN@ IDLE WHAT
john p2 :0.0
I have been having major issues with XFree86 recently. It seems to just
completely halt the machine hard whenever I try starting it. If I run
it from a remote terminal with -verbose all the way up, it seems to halt
at the section just after it says it's loading the RENDER module. I was
wondering i
37 matches
Mail list logo
