date:20130913

RE: mountroot> while booting r255342 memstick

2013-09-13 Thread Uzumaki Naruto

Thanks for this info, Joel
Would try the solution, rebuild the whole thing, kinda new with this.


> Date: Fri, 13 Sep 2013 07:05:18 +0200
> From: j...@vnode.se
> To: narut...@outlook.com
> CC: freebsd-current@freebsd.org; m...@freebsd.org
> Subject: Re: mountroot> while booting r255342 memstick
> 
> On Thu, Sep 12, 2013 at 12:32:12AM +, Uzumaki Naruto wrote:
> > Hi,
> > I downloaded FreeBSD-10.0-CURRENT-amd64-20130907-r255342-memstick.img and 
> > dd into KINGSTON DT 101 G2 1.00 USB pendrive
> 
> Looks similar to what I reported back in February:
> http://lists.freebsd.org/pipermail/freebsd-current/2013-February/039542.html
> 
> mav@ committed a fix for this here:
> http://lists.freebsd.org/pipermail/svn-src-head/2013-February/045143.html
> 
> Perhaps a quirk is needed for your USB pendrive as well. 
> 
> -- 
> Joel
  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: mountroot> while booting r255342 memstick

2013-09-13 Thread Uzumaki Naruto

fyi, I just tried FreeBSD 10 ALPHA memstick

same issue, stuck at mountroot> too.


  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD 10.0-ALPHA1 now available

2013-09-13 Thread Glen Barber

The first ALPHA build of the 10.0-RELEASE release cycle is now available
on the FTP servers for the amd64, i386, ia64, powerpc, and sparc64
architectures.

The image checksums follow at the end of this email.

ISO images and, for architectures that support it, the memory stick images
are available here:

  ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/

(or any of the FreeBSD mirror sites).

If you notice problems, you can report them through the normal GNATS PR
system or here on the -current mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "head/" branch.

Please be aware that cvsup and CVS are not supported methods of updating
the src/ tree.

Important note to freebsd-update(8) users: freebsd-update(8) is not
a supported upgrade path for the 10.0-ALPHA builds.

Checksums:

amd64:
SHA256 (FreeBSD-10.0-ALPHA1-amd64-bootonly.iso) = 
cd175d5412ef53f5502993d80ee5f783ba03e1f6f4efb8a6c294d60cd03c2972
SHA256 (FreeBSD-10.0-ALPHA1-amd64-disc1.iso) = 
8b2a9cdfb95f153f312c63cd1c4cafb49cfb8e2610fdf04763a9e54f197f7dc8
SHA256 (FreeBSD-10.0-ALPHA1-amd64-memstick.img) = 
d2c2fd54f834fa62c6beccbfe3aa53dd6aad6242345e0ea9f40eac1611232e73

MD5 (FreeBSD-10.0-ALPHA1-amd64-bootonly.iso) = 
54a17a5315ff2b4210b3ef8637015276
MD5 (FreeBSD-10.0-ALPHA1-amd64-disc1.iso) = 9224e22668d9f4167c5c2f9a7876a172
MD5 (FreeBSD-10.0-ALPHA1-amd64-memstick.img) = 
aba052abad34d074a44c0a0df28f870b

i386:
SHA256 (FreeBSD-10.0-ALPHA1-i386-bootonly.iso) = 
3bf349764740a5271ba96a471d815e057b16d3ae4286303f50a8b02d42518e34
SHA256 (FreeBSD-10.0-ALPHA1-i386-disc1.iso) = 
c1ddf6661777e7c39f5695c65e205d5ff7a7e98f2c3c78f91c92ea7e6830eb1c
SHA256 (FreeBSD-10.0-ALPHA1-i386-memstick.img) = 
c7af7fc17afb4018d35db6e5aa34d37d05bd0d29994c1cb983ad808cefbedfc5

MD5 (FreeBSD-10.0-ALPHA1-i386-bootonly.iso) = 
75edd55bb3e0ea2a17a0660f29e3114d
MD5 (FreeBSD-10.0-ALPHA1-i386-disc1.iso) = 163e700ec164c38a39aa5868c8531bea
MD5 (FreeBSD-10.0-ALPHA1-i386-memstick.img) = 
5fbf7305cfac91f7342123cfd43f7b02

ia64:
SHA256 (FreeBSD-10.0-ALPHA1-ia64-bootonly.iso) = 
46c3d4c81d6bc35f02091fa052881437e140368dbc261c9f19edf28664d8af47
SHA256 (FreeBSD-10.0-ALPHA1-ia64-disc1.iso) = 
c42ee528ad9fc75d837302220871bb08ed6806117cb2d59b022d57f7f79eaa9f
SHA256 (FreeBSD-10.0-ALPHA1-ia64-memstick.img) = 
95c7cca7f764ebe554356a15cad5ab37c9803fbcede4ac43e63ff013e6ac435d

MD5 (FreeBSD-10.0-ALPHA1-ia64-bootonly.iso) = 
e1e32574ec662a0184556c8a7db86acb
MD5 (FreeBSD-10.0-ALPHA1-ia64-disc1.iso) = ed798a212d99787bf7c8441876d3969f
MD5 (FreeBSD-10.0-ALPHA1-ia64-memstick.img) = 
42f06c9ee4498373ed80543e0c62ca84

powerpc:
SHA256 (FreeBSD-10.0-ALPHA1-powerpc-bootonly.iso) = 
9be0cdda5edd6aec6570e51fc8e1f2cdc6f15235b2dd0cd608455b1e2aeb5729
SHA256 (FreeBSD-10.0-ALPHA1-powerpc-disc1.iso) = 
306275148dd9ae925158c9159c9e40b32cd39c600eff13d73aba85d9af63c884
SHA256 (FreeBSD-10.0-ALPHA1-powerpc-memstick.img) = 
1d05fa7a239fcc163224bae1b19796bf5131ffba742a2a18d2db5d485c072180

MD5 (FreeBSD-10.0-ALPHA1-powerpc-bootonly.iso) = 
1e12ec58faa5a3ab2c5203ddd7e6469d
MD5 (FreeBSD-10.0-ALPHA1-powerpc-disc1.iso) = 
eaa9631d5ea2876e6eedf5e418074598
MD5 (FreeBSD-10.0-ALPHA1-powerpc-memstick.img) = 
15f84226f294c32f6cf1df7668099479

sparc64:
SHA256 (FreeBSD-10.0-ALPHA1-sparc64-bootonly.iso) = 
52b524c150382a06af531312e97be0e6c6d5e348199a20dda0a7d0fec08dd74f
SHA256 (FreeBSD-10.0-ALPHA1-sparc64-disc1.iso) = 
fd9c2e28a2162f8063542ccb813d0b00ef366734bf86b8ad31e8375295385146

MD5 (FreeBSD-10.0-ALPHA1-sparc64-bootonly.iso) = 
9d03833e7f05917acb5252a6f07f3f64
MD5 (FreeBSD-10.0-ALPHA1-sparc64-disc1.iso) = 
1253f05cbdfcf7042524f17a5f590a2b

Glen



pgp1C5BEI7OdH.pgp
Description: PGP signature

Installworld on amd64 fails on libc.a on r255342

2013-09-13 Thread Eir Nym

I get this error for a while, and don't know what to do with.

I build the world, then try to install it into DESTDIR. And at this point I
always get error that libc.a can't be found.

To eliminate any mistakes in commits I've run snapshot r255342 from FTP in
VM and build sources it contains.

my building and installing world with following commands:

 # make toolchain buildworld __MAKE_CONF=/dev/null SRCCONF=src.conf
 # make hierarchy distrib-dirs distribution installworld

some notes:
 * Targets like hierarchy, disturb-dirs and distribution are described in
FreeBSD Handbook in this order
 * Target distribution doesn't install anything, but configuration files.

SRCCONF has following contents:

WITHOUT_AMD="YES"
WITHOUT_ASSERT_DEBUG="YES"
WITHOUT_BIND="YES"
WITH_BMAKE="YES"
WITH_BSD_GREP="YES"
WITH_CLANG="YES"
WITH_CLANG_EXTRAS="YES"
WITH_CLANG_FULL="YES"
WITH_CLANG_IS_CC="YES"
WITH_CTF="YES"
WITHOUT_CTM="YES"
WITHOUT_DYNAMICROOT="YES"
WITHOUT_FLOPPY="YES"
WITH_ICONV="YES"
WITHOUT_HTML="YES"
WITHOUT_IPFILTER="YES"
WITHOUT_IPFW="YES"
WITHOUT_IPX="YES"
WITHOUT_IPX_SUPPORT="YES"
WITH_LDNS_UTILS="YES"
WITH_LIBCPLUSPLUS="YES"
WITH_LIBICONV_COMPAT="YES"
WITHOUT_NCP="YES"
WITHOUT_NIS="YES"
WITHOUT_NLS="YES"
WITHOUT_NLS_CATALOGS="YES"
WITH_OPENSSH_NONE_CIPHER="YES"
WITHOUT_PC_SYSINSTALL="YES"
WITHOUT_RCMDS="YES"
WITHOUT_SYSINSTALL="YES"
WITHOUT_TCSH="YES"
WITH_USB_GADGET_EXAMPLES="YES"

-- Eir Nym
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dns/libidn puzzle

2013-09-13 Thread Walter Hurry

On Fri, 13 Sep 2013 02:44:57 +0200, Matthias Andree wrote:

> Am 12.09.2013 23:44, schrieb Walter Hurry:
>> On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config',
>> I get a dialog asking me whether I want DOCS and/or NLS.
>> 
>> However, on 10-CURRENT (r255358) I get this:
>> 
>> $ cd /usr/ports/dns/libidn $ sudo make config ===> Options unchanged $
>> 
>> Why the difference?
> 
> Is dialog4ports installed on your 10-CURRENT?
> 
Yes, it is. dialog4ports-0.1.5_1

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: mountroot> while booting r255342 memstick

2013-09-13 Thread Uzumaki Naruto

dd back to 10 current

xhci0: 
ehci0: 
ehci1: 

usbus0 on xhci0
usbus1 on ehci0
usbus2 on ehci1

usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
usbus2: 480Mbps High Speed USB v2.0

ugen1.1:  at usbus1
ugen0.1: <0x8086> at usbus0
ugen2.1:  at usbus2

uhub0:  on usbus1
uhub1: <0x8086 XHCI root HUB...> on usbus0
uhub2:  on usbus2
// hub doesn't number accordingly to usbus number?

first test = while pendrive boot from usbus0 (USB 3.0)
-
ugen0.2:  at usbus0
umass0:  on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:3:0:-1: Attached to scbus3

second test = while pendrive boot from usbus1 or usbus2 (first one)
(idk how to number and confirm their number)
---
ugen0.2:  at usbus0
umass0:  on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:3:0:-1: Attached to scbus3

third test = while pendrive boot from usbus1 or usbus2 (another one)
(idk how to number and confirm their number)
---
uhub0: <0x8086 XHCI root HUB...> on usbus0
uhub1:  on usbus2
uhub2:  on usbus1
// different from previous info

ugen1.3:  at usbus1
umass0:  on usbus1
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:3:0:-1: Attached to scbus3

I don't know if the numbering of uhub is changeable based on where user plug in 
their pendrive, seems unusual to me.



  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: mountroot> while booting r255342 memstick

2013-09-13 Thread Uzumaki Naruto

> Also, if you can try the 9.2-RC4 image, that would also be appreciated.
> If this is a problem only with 10.0, this is something re@ and hselasky@
> (bcc'd) needs to be aware of.
> 
> Glen

tried 9.2-RC4 image, (64bit) memstick
same error,
mountroot> ?
List of GEOM managed disk devices:
  ada0s1 ada0 cd0

no diksid compare to 10 current.

and i found one interesting information while scrolling up

let me ascii my laptop usb port below first.
[--] usbus0 top, USB 3.0 (blue)
[--] usbus2 middle, USB 2.0 (black)
[--] usbus1 bottom, USB 2.0 (black)

xhci0:  // my usb 3.0 hole
usbus0 on xhci0
ehci0:  // my usb 2.0 hole first hole
usbus1 on ehci0
ehci1:  // my usb 2.0 hole second hole
usbus2 on ehci1

ugen 1.3:  at usbus1 // assume this info is correct
umass0:2:0:-1: Attached to scbus2 // who is using scbus1 and scbus0

i took out my pendrive from usbus1 and plug it into usbus2, off , wait a few 
second and on the machine since idk how to reboot from mountpoint>.

below the after rebooted info,

ugen0.2:  at usbus0 // why?
umass0:  on usbus0

why usbus0? I didn't plug into USB 3.0?

I scrolled up and this info surprise me, maybe a bug.
xhci0:  // my usb 3.0 hole
usbus0 on xhci0

Is this some sort of error during usbus number assigned?

I hope this information could help everybody to diagnose and solve this issue.

 
> On Fri, Sep 13, 2013 at 11:09:30AM +0900, Lundberg, Johannes wrote:
> > Does it work with the 9.1 image? If it does, you probably have the same
> > problem as I do with the new Macbook Air.
> > Optimisations made to the xhci driver causes it to fail. What I've done is
> > to create a new install image with sys/dev/usb/controller/xhci* reverted
> > back to 243780.
> > 
> > --
> > Johannes Lundberg
> > Project leader and lead developer of Mirama OS (previously Viking OS)
> > BRILLIANTSERVICE CO., LTD.
> > 
> > My blog 
> > Mirama homepage 
> > blog
> > Company homepage 
> > 
> > 
> > On Thu, Sep 12, 2013 at 11:14 AM, Nathan Whitehorn
> > wrote:
> > 
> > > On 09/11/13 20:42, Uzumaki Naruto wrote:
> > >
> > >> If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't
> > >>> support GPT disk type, because OEM Acer only gave GPT supported BIOS for
> > >>> model that pre-loaded with Windows 8.
> > >>>
> > >> Maybe it helps to clarify, this laptop got no UEFI firmware, I could
> > >> convert my hard disk to GPT type using diskpart command, but the
> > >> functionality to boot from GPT partition is unavailable through BIOS.
> > >>
> > >>
> > > Booting from GPT does not require BIOS support. BIOSes don't (or aren't
> > > supposed to -- some broken ones do) parse the partition table at all.
> > > -Nathan
> > >
> > > __**_
> > > freebsd-current@freebsd.org mailing list
> > > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@**
> > > freebsd.org "
> > >
  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ZFS secondarycache on SSD problem on r255173

2013-09-13 Thread Steven Hartland

This is a recent bit of code by Justin cc'ed, so he's likely the best person to
investigate this one.

   Regards
   Steve
- Original Message - 
From: "Dmitryy Makarov" 

To: 
Sent: Friday, September 13, 2013 12:16 PM
Subject: ZFS secondarycache on SSD problem on r255173

Hello, FreeBSD Current. 

Have some trouble with adding SSD drive as secondarycache device on 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r255173 : 
SSD INTEL SSDSC2BW180A4 

dmesg: 
ada1 at ahcich2 bus 0 scbus4 target 0 lun 0 
ada1:  ATA-9 SATA 3.x device 
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) 
ada1: Command Queueing enabled 
ada1: 171705MB (351651888 512 byte sectors: 16H 63S/T 16383C) 
ada1: quirks=0x1<4K> 
ada1: Previously was known as ad8 

# diskinfo -v /dev/ada1 
/dev/ada1 
512 # sectorsize 
180045766656 # mediasize in bytes (167G) 
351651888 # mediasize in sectors 
4096 # stripesize 
0 # stripeoffset 
348861 # Cylinders according to firmware. 
16 # Heads according to firmware. 
63 # Sectors according to firmware. 
BTDA326504N51802GN # Disk ident. 

Creating partition and adding: 
# gpart create -s gpt ada1 
# gpart add -t freebsd-zfs -s3G -l zil0 ada1 
# gpart add -t freebsd-zfs -l cache0 ada1 
# zpool add disk1 log /dev/gpt/zil0 
# zpool add disk1 cache /dev/gpt/cache0 

After that have: 
log 

gpt/zil0 ONLINE 0 0 0 
cache 
gpt/cache0 ONLINE 0 0 0 block size: 512B configured, 4096B native 

But why? ZFS can't properly set sector size for cache device (quirks=0x1<4K>)? 
And have some strange behavior with ZIl partition on the same SSD - everything works! 

Okay, was trying to do some workaround with GNOP: 
# gnop create -S4096 /dev/gpt/cache0 
# zpool add disk1 cache /dev/gpt/cache0.nop 

Seems to be OK 
cache 
gpt/cache0.nop ONLINE 0 0 0 

But after reboot pool has 
status:One or more devices are configured to use a non-native block size. 
Expect reduced performance. 

cache 
gptid/39e40c33-1c4d-11e3-ac20-002590aa9548 ONLINE 0 0 0 block size: 512B configured, 4096B native 

And no gnop parts was found, and even gpart (in /dev/gpart) 

# gnop status 
# gnop: Command 'status' not available. 

# gpart show -l ada1 
=> 34 351651821 ada1 GPT (167G) 
34 6 - free - (3.0k) 
40 6291456 1 zil0 (3.0G) 
6291496 345360352 2 cache0 (164G) 
351651848 7 - free - (3.5k) 

# ls /dev/gpt/cache* 
zsh: no matches found: /dev/gpt/cache* 

Please, help to deal with this problem. 
Or what else information can be useful to find out this trouble. 
___

freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZFS secondarycache on SSD problem on r255173

2013-09-13 Thread Dmitryy Makarov

Hello, FreeBSD Current. 

Have some trouble with adding SSD drive as secondarycache device on 
10.0-CURRENT FreeBSD 10.0-CURRENT #1 r255173 : 
SSD INTEL SSDSC2BW180A4 

dmesg: 
ada1 at ahcich2 bus 0 scbus4 target 0 lun 0 
ada1:  ATA-9 SATA 3.x device 
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) 
ada1: Command Queueing enabled 
ada1: 171705MB (351651888 512 byte sectors: 16H 63S/T 16383C) 
ada1: quirks=0x1<4K> 
ada1: Previously was known as ad8 


# diskinfo -v /dev/ada1 
/dev/ada1 
    512 # sectorsize 
    180045766656    # mediasize in bytes (167G) 
    351651888   # mediasize in sectors 
    4096    # stripesize 
    0   # stripeoffset 
    348861  # Cylinders according to firmware. 
    16  # Heads according to firmware. 
    63  # Sectors according to firmware. 
    BTDA326504N51802GN  # Disk ident. 

Creating partition and adding: 
# gpart create -s gpt ada1 
# gpart add -t freebsd-zfs -s3G -l zil0 ada1 
# gpart add -t freebsd-zfs  -l cache0 ada1 
# zpool add disk1 log /dev/gpt/zil0 
# zpool add disk1 cache /dev/gpt/cache0 

After that have: 
  log 

   gpt/zil0  ONLINE   0 0 0 
 cache 
  gpt/cache0    ONLINE   0 0 0  block size: 512B 
configured, 4096B native 

But why? ZFS can't properly set sector size for cache device (quirks=0x1<4K>)? 
And have some strange behavior with ZIl partition on the same SSD - everything 
works! 


Okay, was trying to do some workaround with GNOP: 
# gnop create -S4096 /dev/gpt/cache0 
# zpool add disk1 cache /dev/gpt/cache0.nop 

Seems to be OK 
 cache 
  gpt/cache0.nop    ONLINE   0 0 0 

But after reboot pool has 
status:One or more devices are configured to use a non-native block size. 
    Expect reduced performance. 

cache 
  gptid/39e40c33-1c4d-11e3-ac20-002590aa9548  ONLINE   0 0 
0  block size: 512B configured, 4096B native 

And no gnop parts was found, and even gpart (in /dev/gpart) 

# gnop status 
# gnop: Command 'status' not available. 

# gpart show -l ada1 
=>  34  351651821  ada1  GPT  (167G) 
 34  6    - free -  (3.0k) 
 40    6291456 1  zil0  (3.0G) 
    6291496  345360352 2  cache0  (164G) 
  351651848  7    - free -  (3.5k) 

# ls /dev/gpt/cache* 
zsh: no matches found: /dev/gpt/cache* 


Please, help to deal with this problem. 
Or what else information can be useful to find out this trouble. 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: Centrino Wireless N2230 support

2013-09-13 Thread Cedric GROSS

Hello,

> De : owner-freebsd-driv...@freebsd.org [mailto:owner-freebsd-
> driv...@freebsd.org] De la part de Matthias Petermann
> Envoyé : vendredi 13 septembre 2013 11:24
> À : freebsd-current@freebsd.org
> Cc : freebsd-wirel...@freebsd.org; freebsd-driv...@freebsd.org
> Objet : Centrino Wireless N2230 support
> 
> 
> Hello,
> 
> there was some recent discussion[1] on freebsd-wireless and freebsd-
> drivers about Centrino Wireless N2230[2] support in FreeBSD.
> 
> I would be curious if there is a working patch somewhere available
> which builds against 10-current?
> 
Not against 10-current.

But if you wish, you could test with my version on github 
https://github.com/KreizIT/FreeBSD-IWN
Use LKGV branch, should be running with 10-current.

Cedric

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-13 Thread S . N . Grigoriev



13.09.2013, 01:11, "Dimitry Andric" :
> On Sep 12, 2013, at 21:47, S.N.Grigoriev  wrote:
>
>>  after upgrading to r255423 (make buildworld && make buildkernel && make 
>> installkernel && make installworld && reboot; make delete-old && make 
>> delete-old-libs) I cannot build the system with the WITH_GCC=yes and 
>> WITH_GNUCXX=yes options in my src.conf. The following error occures:
>>
>>  --- libgssapi_krb5.so.10 ---
>>  building shared library libgssapi_krb5.so.10
>>  --- gnu/lib__L ---
>>  /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:3: 
>> error: use of undeclared identifier '_List_node_base'
>>   _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
>>   ^
>
> I just sent a mail to re@ to get approval for a fix for this.  In the
> mean time, please apply the attached patch.
>
> -Dimitry
>
> ,

Hi Dimitry,

thank you for your response. Your patch works for me!

-- 
Regards,
S.Grigoriev.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Centrino Wireless N2230 support

2013-09-13 Thread Matthias Petermann



Hello,

there was some recent discussion[1] on freebsd-wireless and  
freebsd-drivers about

Centrino Wireless N2230[2] support in FreeBSD.

I would be curious if there is a working patch somewhere available  
which builds against

10-current?

Thanks in advance & kind regards,
Matthias


[1] http://lists.freebsd.org/pipermail/freebsd-drivers/2013-July/001570.html
[2]  
http://www.intel.de/content/www/de/de/wireless-products/centrino-wireless-n-2230.html


--
Matthias Petermann 
Ihr Partner für anspruchsvolle IT-Lösungen
www.petermann-it.de - lösungsorientiert, innovativ und erfolgreich

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: mountroot> while booting r255342 memstick

RE: mountroot> while booting r255342 memstick

FreeBSD 10.0-ALPHA1 now available

Installworld on amd64 fails on libc.a on r255342

Re: dns/libidn puzzle

RE: mountroot> while booting r255342 memstick

RE: mountroot> while booting r255342 memstick

Re: ZFS secondarycache on SSD problem on r255173

ZFS secondarycache on SSD problem on r255173

RE: Centrino Wireless N2230 support

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

Centrino Wireless N2230 support

12 matches

Site Navigation

Mail list logo

Footer information