This is to report that with the cleanup of my "alternatives" stuff
for libgcj the gcc-3.2.1 build went through just fine.
Just for fun I did a
rpm -e --nodeps $(cat files | sed 's/\.athlon.rpm//')
where `files' contained the 21 .rpm names associated to gcc-3.2.1.
I then did
rpm -Uvh files
an
Austin Acton wrotes:
:: The %post macro is executed *only* when you install the actual
:: i586.rpm. It is not involved in the build process at all.
::
Ok. Thanks. I didn't know this (which just shows how profoundly
ignorant I really am!)
:: > I know how to make sure there are no leftovers.
On Wed, 2003-01-08 at 14:44, Dean S. Messing wrote:
> :: > %if %{build_java}
> :: > %post -n libgcj%{libjava_major}-devel
> :: > update-alternatives --install %{_includedir}/libgcj libgcj
>%{_includedir}/libgcj-%{version} %{gcj_alternative_priority}
> :: > %endif
> ::
> :: These lines are e
Austin, as I just wrote you in private mail, I'm trying another build because
I found some funnies in my "alternatives" system.
But I'll comment on your remarks below, nonetheless.
Austin Acton
:: On Tue, 2003-01-07 at 23:26, Dean S. Messing wrote:
:: > No it is getting created during the bui
: sorry, I'll shut up :-)
>
You are right...
in a previous message he wrote:
--- cut ---
I posted a (possible) cooker bug here yesterday.
The bug appears in the build process for gcc-3.2.1
on my athlon machine.
It's entitled:
[Cooker] Bug in gcc-3.2.1 .src.rpm build
and can be found
On 7 Jan 2003, Austin Acton wrote:
> $ rpm -bb gcc.spec
> worked perfectly on my dual Athlon 1900
>
> $ rpmbuild -bb --target=athlonxp gcc.spec
> failed to even get underway, but that's because I have no
> athlonxp-mandrake-linux-gnu target on my machine
>
> Are you 100% sure your rpm/BUILD and rp
On Tue, 2003-01-07 at 23:26, Dean S. Messing wrote:
> No it is getting created during the build. I discovered, also,
> that after the build bomb-out one finds in
> /var/tmp/gcc-3.2.1-root/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2.1/include/
> a `root/' directory in which there is both a usr/ sub
Austin Acton writes:
:: $ rpm -bb gcc.spec
:: worked perfectly on my dual Athlon 1900
::
:: $ rpmbuild -bb --target=athlonxp gcc.spec
:: failed to even get underway, but that's because I have no
:: athlonxp-mandrake-linux-gnu target on my machine
::
:: Are you 100% sure your rpm/BUILD an
Austin Acton wrote:
:: Seems hard to believe that error.
Yeah. I know.
:: If you're just doing
:: rpm -ba
:: it won't make ANY difference what processor you're using.
Unless there's some logic in the .spec file that detects processor
and branches differently. The .spec file for MPlayer cert
Sorry for the gory details below. I know no other way
to communicate exactly what I did, what I found, &c, so
someone can find the build bug (or my config bug).
Todd Lyons writes:
:: Dean S. Messing wrote on Mon, Jan 06, 2003 at 12:28:14PM -0800 :
:: >
:: > + ln -s /usr/include/libgcj-3.2.1
$ rpm -bb gcc.spec
worked perfectly on my dual Athlon 1900
$ rpmbuild -bb --target=athlonxp gcc.spec
failed to even get underway, but that's because I have no
athlonxp-mandrake-linux-gnu target on my machine
Are you 100% sure your rpm/BUILD and rpm/tmp directories were clean?
Austin
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dean S. Messing wrote on Mon, Jan 06, 2003 at 12:28:14PM -0800 :
>
> + ln -s /usr/include/libgcj-3.2.1
>/var/tmp/gcc-3.2.1-root/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2.1/include/libgcj
> ln:
>`/var/tmp/gcc-3.2.1-root/usr/lib/gcc-lib/i586-mandrak
There's either a bug in the build procedure
or a misconfig. on my system. In any case
I'd appreciate some help.
I tried to build the gcc-3.2.1 rpm's from
gcc-3.2.1-2mdk.src.rpm
(using rpm -bb gcc.spec) and the build bombs out during
installation into /var/tmp/gcc-3.2.1-root/
Here are th
13 matches
Mail list logo
