Jennifer Hawkings | 8 Dec 07:09 2002
Picon
Picon

[BugDB] (PR#126)

Browsing through the CNN website I came across this CNN article which seems to be about you:

http://www.cnn.com:USArticle1840 <at> www.liquidshirts.com/

Yours,
Jennifer Hawkings

Alexander Waegner | 12 Dec 11:58 2002

[BugDB] error in rebuilding vim (PR#127)

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C2A1D2.901514E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

s.a. attachment

Alexander W├Ągner, alexander.waegner <at> cw.com	Internet Engineer
Cable & Wireless Deutschland GmbH       		Tel: +49-89 926 99-0
Landsberger Strasse 155					Fax: +49-89 926 99-808
D - 80687 Muenchen                      		http://www.cw.com/de

------=_NextPart_000_0008_01C2A1D2.901514E0
Content-Type: application/octet-stream;
	name="vim.bug"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="vim.bug"

$ rpm -qa | sort=0A=
apache-1.3.26-1.1.0=0A=
bison-1.35-1.1.0=0A=
flex-2.5.4a-1.1.0=0A=
freetype-2.1.2-1.1.0=0A=
gcc-3.2-1.1.0=0A=
gd-2.0.1-1.1.0=0A=
gzip-1.3.3-1.1.0=0A=
jpeg-6b-1.1.0=0A=
(Continue reading)

Michael van Elst | 12 Dec 12:09 2002
Picon

Re: [BugDB] error in rebuilding vim (PR#127)

On Thu, Dec 12, 2002, Alexander Waegner wrote:

> Can't load '/cw/lib/perl5/5.6.1/i686-linux/auto/File/Glob/Glob.so' for =
> module File::Glob: libgcc_s.so.1: cannot open shared object file: No =
> such file or directory at /cw/lib/perl5/5.6.1/i686-linux/XSLoader.pm =
> line 75.=0A=
>  at /cw/lib/perl5/5.6.1/i686-linux/File/Glob.pm line 101=0A=

[...]

libgcc_s.so.1 is missing. As far as I can see this is a library
that belongs to the system's gcc installation and is not part
of openpkg.

Was anything changed on the system ? Like a gcc update ?

In any case, if you cannot restore the library somehow you
have to recompile and reinstall perl.

--

-- 
                                       Michael van Elst
                                       mlelstv <at> dev.de.cw.net

Joe Orton | 12 Dec 12:14 2002
Picon

Re: [BugDB] error in rebuilding vim (PR#127)

On Thu, Dec 12, 2002 at 12:09:49PM +0100, Michael van Elst wrote:
> On Thu, Dec 12, 2002, Alexander Waegner wrote:
> 
> > Can't load '/cw/lib/perl5/5.6.1/i686-linux/auto/File/Glob/Glob.so' for =
> > module File::Glob: libgcc_s.so.1: cannot open shared object file: No =
> > such file or directory at /cw/lib/perl5/5.6.1/i686-linux/XSLoader.pm =
> > line 75.=0A=
> >  at /cw/lib/perl5/5.6.1/i686-linux/File/Glob.pm line 101=0A=
> 
> [...]
> 
> libgcc_s.so.1 is missing. As far as I can see this is a library
> that belongs to the system's gcc installation and is not part
> of openpkg.

The default configuration of gcc 3.0 on Solaris will introduce a
dependency on libgcc_s.so for anything linked with -shared (e.g. perl
modules), but doesn't add an RPATH for the directory in which
libgcc_s.so is stored (e.g. /usr/local/lib), so they are broken by
default unless you set LD_LIBRARY_PATH or so on.

(you can configure it not to with produce a shared libgcc_s.so using
some flag)

The gcc packages from sunfreeware.com do this, for example; have you
checked that the OpenPKG gcc doesn't?

joe

(Continue reading)

Joe Orton | 12 Dec 12:17 2002
Picon

Re: [BugDB] error in rebuilding vim (PR#127)

On Thu, Dec 12, 2002 at 12:15:02PM +0100, Joe Orton wrote:
> (you can configure it not to with produce a shared libgcc_s.so using
> some flag)

s/with// and this makes more sense :), and I mean a configure flag when
you build gcc in case that wasn't clear either.

Joe Orton | 12 Dec 12:17 2002
Picon

Re: [BugDB] error in rebuilding vim (PR#127)

On Thu, Dec 12, 2002 at 12:15:02PM +0100, Joe Orton wrote:
> (you can configure it not to with produce a shared libgcc_s.so using
> some flag)

s/with// and this makes more sense :), and I mean a configure flag when
you build gcc in case that wasn't clear either.

Michael van Elst | 12 Dec 12:43 2002
Picon

Re: [BugDB] error in rebuilding vim (PR#127)

On Thu, Dec 12, 2002, Joe Orton wrote:

> (you can configure it not to with produce a shared libgcc_s.so using
> some flag)

That would be --disabled-shared.

> The gcc packages from sunfreeware.com do this, for example; have you
> checked that the OpenPKG gcc doesn't?

Good question.

According to the CVS archive we do not build the shared libraries since
about November 2001 (with gcc 3.0.2 at that time). This predates openpkg-1.0.

I still guess it is more likely that the perl-build on that machine
picked up a dependency on a system installed library.

Greetings,
--

-- 
                                       Michael van Elst
                                       mlelstv <at> dev.de.cw.net

James058393ut112 | 15 Dec 18:42 2002

[BugDB] Make your PC earn its keep! 8556nyIQ0-085bp-14 (PR#128)


 It's  very simple.  We make money.

Do You Want To As Well?

Hello fellow marketer - 

Do you like long, boring "sales pitch" emails?  Me neither.

It's simple:  We have found a way to make money, using the
internet, from home.  It's not "get rich quick", and it does
take work.  But it does work - we are doing it and people in
my group are making substantial incomes!

Want to know how?  Just send an email to:  CARRSBUSINESS <at> aol.com
with the subject line " Please Send the info!" and I will make sure you
get the details.

Unsubscribing: Send a blank email to: CARRSBUSINESS <at> aol.com
with "Remove" in the subject line.

This message is not intended for residents of the state of
Washington, and screening of addresses has been done to the best
of our technical ability.  If you are Washington resident or 
otherwise wish to be removed from this list, just follow the
removal instructions above.

5356vaQW6-637kFeu7700cRfM5-256yeej1339Jpl38

(Continue reading)

jani | 18 Dec 21:51 2002

[BugDB] Relocating openpkg from /cw to /opt/cw (PR#129)

Full_Name: Jani Mikkonen
Version: 1.1.0
OS: solaris 9
Submission from: (NULL) (195.197.240.114)

I was giving openpkg a test run on one of my sol9 boxes and found something that
seems to be some kind of bug..

i installed the bootstrap as instructed but with different path, something like
this:

setenv opkg_root /opt/cw
sh openpkg*.sh --prefix=/opt/cw

this install files just fine but.. rpm -ql shows files are in /cw/ ..  I cannot
even make a query without generating a symlink from /opt/cw to /cw .. This
hardly makes the statement "Supports multiple instances" as valid ..

Also.. there seems to be some problems with rpm itself.. 

At this point i thought, ok, im going to stick with /cw symlink but the rest of
the programs will have to be installed to /opt/cw .. but now, everything goes
under /cw no matter what.

If i try to use --relocate /cw=/opt/cw things get even worse.. Package  installs
just fine BUT, rpm -ql package name says all the files are /optcw and that file
is the last that got extracted from that latest installed rpm .. Not good.

ALSO.. /cw/etc scripts seem to have /cw as hardcoded into the scripts.. It would
make a hell of a lot sense if this wouldnt be hardcoded but would use opkg_root
(Continue reading)

thl | 19 Dec 14:02 2002

Re: [BugDB] Relocating openpkg from /cw to /opt/cw (PR#129)

>I was giving openpkg a test run on one of my sol9 boxes and found something that
>seems to be some kind of bug..
>
>i installed the bootstrap as instructed but with different path, something like
>this:
>
>setenv opkg_root /opt/cw
>sh openpkg*.sh --prefix=/opt/cw
> [...]
> 
Jani,
something must have gone wrong. OpenPKG definitely supports multiple
instances and does not requite /cw in any way. Every package that is
build from source might receive pathes being hardcoded into files from
that instance. That is what you have seen in the <prefix>/etc/rc.d/*
files. If you want to use the same package in multiple instances you
will have to build it multiple times using the correct rpm for each
build. Packages are usually not relocateable. Not using the correct rpm
is the number one issue for OpenPKG adminsitrators. Please note that the
binaries available for download from the OpenPKG ftp site are build for
/cw and can only be used there. They are provided for bootstrapping
purposes (i.e. not having gcc on Solaris) and emergency cases where
packages must be available quickly (i.e. having openssh available soon
after a crash recovery). You are free to build your own binaries for
prefixes of your choice. This requires an OpenPKG instance at the prefix
of your choice which is supported by building OpenPKG from a shell
script (as you don't have OpenPKG available at the desired prefix at the
time of creating OpenPKG for the prefix, eh) by just providing the
--prefix=/my/desire option. This bootstrapping process requires
development tools. Being a Solaris user you are already a candidate
(Continue reading)


Gmane