Hi.
In <[EMAIL PROTECTED]>, Will Andrews wrote:
>Um.. objprelink is disabled if OSVERSION >= 500029. So it is
>already "ripped out" for -current.
>
I think it better to rip objprelink out of kde port on -CURRENT, too. On
my -CURRENT (updated in Mar 11), many kde binaries build with using
objpr
Hi.
In <[EMAIL PROTECTED]>, Maxim M. Kazachek wrote:
>I've installed qt23 from ports painlessly
>
Does uic command provided by qt23 port work on your system? On my
-CURRENT (updated in Mar 11), that binary was linked with weird
liblcms.so_edata as next:
% ldd uic
uic:
libqutil.so.1 => /
I've recompiled kernet right before building qt... And have great prob
with compiling -CURRENT right before Mar 8... I've installed -CURRENT SNAP
on 20020219 which seems have broken binutils... Because xv and some other
my packages coredumped with bus error (libpng issue, seemed to be solved
Feb 2
Hiten Pandya <[EMAIL PROTECTED]> writes:
> I have a tru 5.0-CURRENT environment.. also.. is there any changes where
> my ENABLE_NLS dillema can be solved..
s/dillema/dilemma/. It's not a dilemma, anyway; it's an issue, a
condition, a situation, a problem, a failure; a conundrum (though not
in th
On Thu, Mar 14, 2002 at 05:54:40PM -0800, Alex Zepeda wrote:
> As far as Qt goes, rip out that objprelink crap. Without it Qt will build
> and work just fine. At least Qt 3.whatever works for me. I don't know
> why objprelink isn't working correctly for Qt, but I don't really care.
> For me d
On Thu, Mar 14, 2002 at 09:01:47PM -0800, Terry Lambert wrote:
> I think it's idiotic to put spackle over the broken window,
> paint the wall, and then call it "fixed".
I know what objprelink is, and as far as I'm concerned it's there to work
around the substandard support that C++ gets from the
On Thu, Mar 14, 2002 at 10:16:14PM -0800, Peter Wemm wrote:
> Alex Zepeda wrote:
> > On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
> >
> > > The compile problems seem to be related to recent compiler toolchain
> > > changes, which you might not see unless you recompiled everythin
Alex Zepeda wrote:
> On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
>
> > The compile problems seem to be related to recent compiler toolchain
> > changes, which you might not see unless you recompiled everything qt23
> > depends on from scratch (which the package cluster does).
>
Alan Eldridge wrote:
> On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote:
> >Alex Zepeda wrote:
> >> As far as Qt goes, rip out that objprelink crap. Without it Qt will build
> >> and work just fine. At least Qt 3.whatever works for me. I don't know
> >> why objprelink isn't working
On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote:
> Alex Zepeda wrote:
> > As far as Qt goes, rip out that objprelink crap. Without it Qt will build
> > and work just fine. At least Qt 3.whatever works for me. I don't know
> > why objprelink isn't working correctly for Qt, but I do
On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote:
>Alex Zepeda wrote:
>> As far as Qt goes, rip out that objprelink crap. Without it Qt will build
>> and work just fine. At least Qt 3.whatever works for me. I don't know
>> why objprelink isn't working correctly for Qt, but I don't
Alex Zepeda wrote:
> As far as Qt goes, rip out that objprelink crap. Without it Qt will build
> and work just fine. At least Qt 3.whatever works for me. I don't know
> why objprelink isn't working correctly for Qt, but I don't really care.
> For me disabling WITNESS does more than enough to ma
On Thu, Mar 14, 2002 at 06:56:53PM -0800, Alex Zepeda wrote:
> On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
>
> > The compile problems seem to be related to recent compiler toolchain
> > changes, which you might not see unless you recompiled everything qt23
> > depends on from s
On Thu, Mar 14, 2002 at 06:56:53PM -0800, Alex Zepeda wrote:
> On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
>
> > The compile problems seem to be related to recent compiler toolchain
> > changes, which you might not see unless you recompiled everything qt23
> > depends on from s
On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
> The compile problems seem to be related to recent compiler toolchain
> changes, which you might not see unless you recompiled everything qt23
> depends on from scratch (which the package cluster does).
Right, when I tried to compil
On Fri, Mar 15, 2002 at 08:36:29AM +0600, Maxim M. Kazachek wrote:
> I've installed qt23 from ports painlessly
Fine, I'm glad to hear it :)
The compile problems seem to be related to recent compiler toolchain
changes, which you might not see unless you recompiled everything qt23
depends on from
I've installed qt23 from ports painlessly
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote:
> I'm just uploading a new 5.x package set. This run was better than
> the previous (5364 packages vs. 5123 for the last run, but far fewer
> than the 5973 packages which are building in 4.x), but there were
> still a number of signi
--- David O'Brien <[EMAIL PROTECTED]> wrote:
> Will you be doing a run on a Tru5-CURRENT box?
> Some of these it is hard to say anything about due to the very special
> environment you built them under.
I have a tru 5.0-CURRENT environment.. also.. is there any changes where
my ENABLE_NLS dillema
On Thu, Mar 14, 2002 at 04:41:59PM -0800, David O'Brien wrote:
> On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote:
> > I'm just uploading a new 5.x package set. This run was better than
> > the previous (5364 packages vs. 5123 for the last run, but far fewer
> > than the 5973 package
On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote:
> I'm just uploading a new 5.x package set. This run was better than
> the previous (5364 packages vs. 5123 for the last run, but far fewer
> than the 5973 packages which are building in 4.x), but there were
> still a number of signif
21 matches
Mail list logo
