[rock-user] please unsuscribe me

"DUBOISSET" <[email protected]> Mon, 25 Apr 2005 14:59:31 +0200
Newsgroups gmane.linux.distributions.rock.user
Message-ID <[email protected]>

-----Message d'origine-----
De : [email protected]
[mailto:[email protected]] De la part de
[email protected]
Envoyé : samedi 23 avril 2005 12:01
À : [email protected]
Objet : rock-user Digest, Vol 12, Issue 5


Send rock-user mailing list submissions to
	[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.rocklinux.net/mailman/listinfo/rock-user
or, via email, send a message with subject or body 'help' to
	[email protected]

You can reach the person managing the list at
	[email protected]

When replying, please edit your Subject line so it is more specific than
"Re: Contents of rock-user digest..."


Today's Topics:

   1. (Cross-)Building trunk for AMD64 (Bernd Petrovitsch)
   2. Re: (Cross-)Building trunk for AMD64 (Clifford Wolf)
   3. Package download for 2.0-stable doesn't find	libtiff-3.7.1
      (Bernd Petrovitsch)
   4. Re: (Cross-)Building trunk for AMD64 (Bernhard C. Schrenk)
   5. Re: (Cross-)Building trunk for AMD64 (Bernd Petrovitsch)
   6. Re: (Cross-)Building trunk for AMD64 (Clifford Wolf)
   7. Re: (Cross-)Building trunk for AMD64 (Clifford Wolf)
   8. Re: (Cross-)Building trunk for AMD64 (Bernd Petrovitsch)
   9. Re: Package download for 2.0-stable doesn't find
      libtiff-3.7.1 (Tobias Hintze)


----------------------------------------------------------------------

Message: 1
Date: Fri, 22 Apr 2005 13:50:25 +0200
From: Bernd Petrovitsch <[email protected]>
Subject: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain

Ends with:
----  snip  ----
== 13:47:00 =[1]=> Building base/dietlibc [0.27 0].
-> Preparing configuration to build this package with dietlibc
(statically).
-> This package does not utilize a C library ...
-> Reading package configuration from package directory. Preparing build

-> in src.dietlibc.1114170404.16393.3870095289
-> Building. Writing output to $root/var/adm/logs/1-dietlibc.out
!> gcc -c dummy.c
!> ar cru bin-x86_64/libcrypt.a dummy.o
!> rm -f dummy.c dummy.o
!> x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem i .. !>
bin-x86_64/dietlibc.a: could not read symbols: Archive h .. !> collect2:
ld returned 1 exit status !> make: *** [bin-x86_64/diet] Error 1
-> $root/var/adm/logs/1-dietlibc.out -> 1-dietlibc.err
== 04/22/05 13:51:44 =[1]=> Aborted building package dietlibc.

Searching for old liggering files ...
-> No errors found.

Creating 2nd stage filesystem:
-> Extracting the packages archives.
-> Saving boot/* - we do not need this on the 2nd stage ...
mv: cannot stat `boot/*': No such file or directory
----  snip  ----

src.dietlibc.1114170404.16393.3870095289/ERROR-LOG ends with:
----  snip  ----
touch dummy.c
gcc -c dummy.c
ar cru bin-x86_64/libcrypt.a dummy.o
rm -f dummy.c dummy.o
x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem include -Os
-fstrict-aliasing -momit-leaf-frame-pointer -mfancy-math-387 -Wall -W
-Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations
-Wno-switch -Wno-unused -Wredundant-decls -nostdlib -o bin-x86_64/diet
bin-x86_64/start.o bin-x86_64/dyn_start.o diet.c bin-x86_64/dietlibc.a
bin-x86_64/dyn_stop.o
-DDIETHOME=\"/usr/src/ROCK/trunk/src.dietlibc.1114170404.16393.387009528
9/dietlibc-0.27\" -DVERSION=\"dietlibc-0.27\" -lgcc
bin-x86_64/dietlibc.a: could not read symbols: Archive has no index; run
ranlib to add one
collect2: ld returned 1 exit status
make: *** [bin-x86_64/diet] Error 1
--- BUILD ERROR ---
Creating file list and doing final adaptions ... 
Processing static lib corrections ...
Verifing the .la files ...
Found 0 files for this package.
Applying package split: 40 dietlibc:dev (/lib/.*\.(la|a|o)$|/include/)
Applying package split: 42 dietlibc:dev /pkgconfig/ Applying package
split: 60 dietlibc:doc /share/doc/ Making post-install adaptions.
Finished building dietlibc=dietlibc.
----  snip  ----

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services





------------------------------

Message: 2
Date: Fri, 22 Apr 2005 14:10:17 +0200
From: Clifford Wolf <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Hi,

On Fri, Apr 22, 2005 at 01:50:25PM +0200, Bernd Petrovitsch wrote:
> Ends with:
> ----  snip  ----
> == 13:47:00 =[1]=> Building base/dietlibc [0.27 0].
> !> x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem i .. !> 
> bin-x86_64/dietlibc.a: could not read symbols: Archive h .. !> 
> collect2: ld returned 1 exit status

yea - I remember - there was something... 

I've just started a bootdisk cross-build for amd64 to see if I can
reproduce that problem..

yours,
 - clifford

-- 
bash -c "gcc -o mysdldemo -Wall -O2 -lSDL -lm -pthread -x c <( echo -e '
#include <SDL/SDL.h>\n#include <complex.h>\nint
main(){SDL_Surface*s;SDL_Event e;int
x,y,n;SDL_Init(SDL_INIT_VIDEO);s=SDL_SetVideoMode(640,480,32,0);for(x=0;
x<640;x++)for(y=0;y<480;y++){float _Complex z=0, c=((x-400)/200.0) +
((y-240)/
200.0)*1.0fi;for(n=1;n<64;n++){z=z*z+c;if(cabsf(z)>2){((Uint32*)s->pixel
s)[x+y
*640]=n<<3;n=99;}}}SDL_UpdateRect(s,0,0,s->w,s->h);do SDL_WaitEvent(&e);
while (e.type!=SDL_QUIT&&e.type!=SDL_KEYDOWN);SDL_Quit();return 0;}' );
./mysdldemo"
 
When your hammer is C++, everything begins to look like a thumb.
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.rocklinux.net/pipermail/rock-user/attachments/20050422/19813b
bc/attachment-0001.bin

------------------------------

Message: 3
Date: Fri, 22 Apr 2005 15:39:58 +0200
From: Bernd Petrovitsch <[email protected]>
Subject: [rock-user] Package download for 2.0-stable doesn't find
	libtiff-3.7.1
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain

Neither on gd.tuwien.ac.at nor on rock.inode.at:
----  snip  ----
17#cat src/Download-Errors
22 download/rene/libtiff/tiff-3.7.1.tar.bz2
          http://rock.inode.at/ROCK-2.0//rene/libtiff/tiff-3.7.1.tar.bz2
22 download/rene/libtiff/tiff-3.7.1.tar.gz
               ftp://ftp.remotesensing.org/pub/libtiff/tiff-3.7.1.tar.gz
----  snip  ----
[ Line breaks by /me ]

Apparently 3.7.2 is the only current version according to
ftp://ftp.remotesensing.org/pub/libtiff/

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services





------------------------------

Message: 4
Date: Fri, 22 Apr 2005 15:41:19 +0200 (CEST)
From: "Bernhard C. Schrenk" <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: "ROCK Users Mailing List" <[email protected]>
Message-ID:
	
<14022.80.120.140.129.1114177279.squirrel-2RFepEojUI34Xx4uTsVUmTJm1M4ZQ9CX@public.gmane.org>
Content-Type: text/plain;charset=iso-8859-1

Hi,

I do not know what I have done different as I tried a cross build for
AMD64 but I have the log files and I found a difference:

On Fri, April 22, 2005 1:50 pm, Bernd Petrovitsch said:
> !> gcc -c dummy.c
> !> ar cru bin-x86_64/libcrypt.a dummy.o
> !> rm -f dummy.c dummy.o
> !> x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem i ..

My log says:
     x86_64-unknown-linux-gnu-gcc -c dummy.c
     x86_64-unknown-linux-gnu-ar cru bin-x86_64/libcrypt.a dummy.o
     rm -f dummy.c dummy.o
     x86_64-unknown-linux-gnu-gcc --specs=specs -isystem include -Os

So there are the cross-gcc and cross-ar called instead. And also during
building bin-x86_64/dietlibc.a my log file shows the cross-ar. Maybe
this is a hint in finding the problem.

Regards,
Bernhard




------------------------------

Message: 5
Date: Fri, 22 Apr 2005 15:50:38 +0200
From: Bernd Petrovitsch <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain

On Fri, 2005-04-22 at 15:41 +0200, Bernhard C. Schrenk wrote:

> I do not know what I have done different as I tried a cross build for 
> AMD64 but I have the log files and I found a difference:
> 
> On Fri, April 22, 2005 1:50 pm, Bernd Petrovitsch said:
> > !> gcc -c dummy.c
> > !> ar cru bin-x86_64/libcrypt.a dummy.o
> > !> rm -f dummy.c dummy.o
> > !> x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem i ..
> 
> My log says:
>      x86_64-unknown-linux-gnu-gcc -c dummy.c
>      x86_64-unknown-linux-gnu-ar cru bin-x86_64/libcrypt.a dummy.o
>      rm -f dummy.c dummy.o
>      x86_64-unknown-linux-gnu-gcc --specs=specs -isystem include -Os
> 
> So there are the cross-gcc and cross-ar called instead. And also 
> during building bin-x86_64/dietlibc.a my log file shows the cross-ar. 
> Maybe this is a hint in finding the problem.

Funny. I simply configured the bootdisk target through `scripts/config
-cfg ...`, downloaded the -required packages and let it Build-Target.
Which part of the config is interesting?

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services





------------------------------

Message: 6
Date: Fri, 22 Apr 2005 15:55:07 +0200
From: Clifford Wolf <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

On Fri, Apr 22, 2005 at 03:41:19PM +0200, Bernhard C. Schrenk wrote:
> On Fri, April 22, 2005 1:50 pm, Bernd Petrovitsch said:
> > !> gcc -c dummy.c
> > !> ar cru bin-x86_64/libcrypt.a dummy.o
> > !> rm -f dummy.c dummy.o
> > !> x86_64-unknown-linux-gnu-gcc-34 --specs=specs -isystem i ..
> 
> My log says:
>      x86_64-unknown-linux-gnu-gcc -c dummy.c
>      x86_64-unknown-linux-gnu-ar cru bin-x86_64/libcrypt.a dummy.o
>      rm -f dummy.c dummy.o
>      x86_64-unknown-linux-gnu-gcc --specs=specs -isystem include -Os

same here. (my bootdisk crossbuild just finished)

maybe there is somethign in your environment which is confusing the
build scripts? Please post the file

	src.dietlibc.[MANYNUMBERSHERE]/debug.buildenv

so I can compare it with my environment.

(that file it is quite big - so it would be great if you could put it
somewhere on the web and just post the link here)

besides, you might need this patch for cross-builds - or the build will
fail later:

	
https://www.rocklinux.net/submaster/smadm.cgi?i=2005042215410213821

yours,
 - clifford

-- 
|    ***** http://www.clifford.at/frame.cgi?cartoons *****    |
| http://www.userfriendly.org        http://www.megatokyo.com |
| http://www.machall.com      ''~``    http://www.ucomics.com |
| http://www.dilbert.com     ( o o )       http://sinfest.net |
+-----------------------.oooO--(_)--Oooo.---------------------+
 
Hoffnung ist der erste Schritt auf der Strasse der Enttaeuschung.
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.rocklinux.net/pipermail/rock-user/attachments/20050422/db08c6
c8/attachment-0001.bin

------------------------------

Message: 7
Date: Fri, 22 Apr 2005 15:57:52 +0200
From: Clifford Wolf <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

On Fri, Apr 22, 2005 at 03:50:38PM +0200, Bernd Petrovitsch wrote:
> Funny. I simply configured the bootdisk target through `scripts/config

> -cfg ...`, downloaded the -required packages and let it Build-Target.
> Which part of the config is interesting?

The config/.../config_usr file. For my test build it was:

--snip--
#
# ROCK Linux TRUNK User Config File
#
ROCKCFGUSR_ARCH='x86'
ROCKCFGUSR_CROSSBUILD='1'
ROCKCFGUSR_EXPERT='1'
ROCKCFGUSR_TARGET='bootdisk'
ROCKCFGUSR_X86_BITS='64'
--snap--

(this file contains all the settings which are not on the default
values, not including stuff which is put in an extra file such as custom
kernel
configurations)

yours,
 - clifford

-- 
| Clifford Wolf /-----=[ www.clifford.at ]==[ Tel: +43-699-10063494 ]=-\

|--------------/ www.cngw.org - www.ccc.de =[ Fax: +43-2235-42788-4 ]=-|

|-=[ EDEN Creations -- www.edenevents.at ]==[ IRC: www.freenode.net ]=-|
\==[ www.rocklinux.org ]===[ www.rocklinux.net ]===[ www.linbit.com ]==/
 
/lusr/bin/brain: received signal: SIGIDIOT
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www.rocklinux.net/pipermail/rock-user/attachments/20050422/45df9d
d4/attachment-0001.bin

------------------------------

Message: 8
Date: Fri, 22 Apr 2005 18:23:07 +0200
From: Bernd Petrovitsch <[email protected]>
Subject: Re: [rock-user] (Cross-)Building trunk for AMD64
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain

On Fri, 2005-04-22 at 15:57 +0200, Clifford Wolf wrote:
> On Fri, Apr 22, 2005 at 03:50:38PM +0200, Bernd Petrovitsch wrote:
> > Funny. I simply configured the bootdisk target through 
> > `scripts/config -cfg ...`, downloaded the -required packages and let

> > it Build-Target. Which part of the config is interesting?
> 
> The config/.../config_usr file. For my test build it was:
> 
> --snip--
> #
> # ROCK Linux TRUNK User Config File
> #
> ROCKCFGUSR_ARCH='x86'
> ROCKCFGUSR_CROSSBUILD='1'

Grrmmmmllll, this was missing.
Apparently I'm too dumb for the simple user interface.

> ROCKCFGUSR_EXPERT='1'
> ROCKCFGUSR_TARGET='bootdisk'
> ROCKCFGUSR_X86_BITS='64'
> --snap--

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services





------------------------------

Message: 9
Date: Sat, 23 Apr 2005 11:55:57 +0200
From: Tobias Hintze <[email protected]>
Subject: Re: [rock-user] Package download for 2.0-stable doesn't find
	libtiff-3.7.1
To: ROCK Users Mailing List <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-15

On Fri, Apr 22, 2005 at 03:39:58PM +0200, Bernd Petrovitsch wrote:
> Neither on gd.tuwien.ac.at nor on rock.inode.at:
> ----  snip  ----
> 17#cat src/Download-Errors
> 22 download/rene/libtiff/tiff-3.7.1.tar.bz2
>           
> http://rock.inode.at/ROCK-2.0//rene/libtiff/tiff-3.7.1.tar.bz2
> 22 download/rene/libtiff/tiff-3.7.1.tar.gz
>
ftp://ftp.remotesensing.org/pub/libtiff/tiff-3.7.1.tar.gz

oh - yes. my fault. i forgot to download everything on the master. does
not seem to be in cron. downloading just now - should be fine in a few.

th
--

> ----  snip  ----
> [ Line breaks by /me ]
> 
> Apparently 3.7.2 is the only current version according to 
> ftp://ftp.remotesensing.org/pub/libtiff/
> 
> 	Bernd
> -- 
> Firmix Software GmbH                   http://www.firmix.at/
> mobil: +43 664 4416156                 fax: +43 1 7890849-55
>           Embedded Linux Development and Services
> 
> 
> 
> _______________________________________________
> rock-user mailing list
> [email protected] 
> http://www.rocklinux.net/mailman/listinfo/rock-user

-- 
Tobias Hintze http://hbs-solutions.de
HBS solutions GbR - Network & Information Systems


------------------------------

_______________________________________________
rock-user mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-user


End of rock-user Digest, Vol 12, Issue 5
****************************************